[Octave-bug-tracker] [bug #42708] Breakpoints should be removed from files when changes are saved

[Richard]

URL:
  <http://savannah.gnu.org/bugs/?42708>

                 Summary: Breakpoints should be removed from files when
changes are saved
                 Project: GNU Octave
            Submitted by: crobar
            Submitted on: Tue 08 Jul 2014 14:29:35 GMT
                Category: GUI
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Other
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: GNU/Linux

    _______________________________________________________

Details:


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:


function parse_breakpoint_test ()
    x = 1;
    x = x + 1;
end



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.




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?42708>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/