Tue 08 Jul 2014 02:29:35 PM UTC, original submission:
Breakpoints should probably be cleares (or greyed out, or otherwise modified) in the GUI editor when a file with a break points present already is edited and saved to avoid the following behaviour:
Take a function like below:
1. run in terminal, to make sure function is loaded by octave
2. put breakpoint on line 2 (x = 1)
3. edit parse_breakpoint_test () and create a parse error, e.g. modify x = x + 1; to be x = x + ; and save the file
4. run the function again (debugger will stop at line 2, either continue, getting the parse error or quit)
You will now be unable to deselect the break point symbol you created in step 1 which remains showing in the editor. Even after you save the file with the parse error fixed. This persists even if you run the file again, and you can place working break points as normal on the other lines which work.
You cannot now place a break point on this original break point line via the editor. You can still place one using dbstop however, and clicking on the break point in the editor still removes the brek point (although the symbol stays there, and you still can't add it back in again via the editor).
The only way you can 'reset' the editor behaviour I have found so far is to close the file and reopen it.
|