Closed
Bug 896217
Opened 12 years ago
Closed 12 years ago
ff caches breakpoints improperly, doesn't break at correct points
Categories
(DevTools :: Debugger, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: jmichae3, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:22.0) Gecko/20100101 Firefox/22.0 (Beta/Release)
Build ID: 20130618035212
Steps to reproduce:
1.add some breakpoints to http://jesusnjim.com/bugs/ff-debugger-cant-set-breakpoints.html#app in the HTML file at lines 507,511,515.
2. hit f5 to run code.
3. hit play button until code runs through.
4. remove 511 and 507 and add 510.
5. hit f5 to run code.
6. hit play/run button to run to next breakpoint.
Actual results:
code will probably stop at old breakpoints, without there being a breakpoint there anymore.hitting play/run button runs code to completion, kind of, if you have more breakpoints elsewhere. it's not completely a run without breakpoints and it's not completely a run and stop at next breakpoint. with the breakpoints I have set here, it runs to completion and skips past the breakpoints.
Expected results:
should continue running the code past those formerly deleted breakpoints and stop.
debugger should stop at next breakpoint when play/run button is hit (unless you want to add another button that does this).
![]() |
||
Updated•12 years ago
|
Component: Untriaged → Developer Tools: Debugger
Comment 1•12 years ago
|
||
Not sure which bug fixed the behavior you were seeing, but this seems to work for me on latest Nightly (Firefox 25). Please reopen if you find otherwise.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Updated•7 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•