My favorites | Sign in
Project Home Wiki Issues
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 3168: Guess the line number of persistent breakpoints
2 people starred this issue and may be notified of changes. Back to list
Status:  Triaged
Owner:  ----
Cc:  sebastia...@gmail.com, odva...@gmail.com
1.5


Sign in to add a comment
 
Project Member Reported by johnjbar...@johnjbarton.com, Jun 22, 2010
Currently persistent breakpoints can be set on the wrong line if the source changes. We should store the source line and if the text does not match, look around for it.

Also we should stay "not executable" instead of "undefined" for breakpoints on lines that are not executable.

Also need at test case for persistent breakpoints...
Oct 30, 2012
Project Member #1 sebastia...@gmail.com
Issue 4474 describes exact source matching for the case a script is called with different parameters.

To clarify what this issue is about:
The debugger should be smart enough to search around the line specified in breakpoints.json and try to match the source code the breakpoint was set for previously.

A similar request is described in issue 4474.

I created a test case for this:
https://getfirebug.com/tests/manual/issues/3168/issue3168.html

Sebastian
Summary: Guess the line number of persistent breakpoints
Owner: ---
Cc: sebastia...@gmail.com odva...@gmail.com
Labels: Test-case-available
Sign in to add a comment

Powered by Google Project Hosting