[Octave-bug-tracker] [bug #60889] Debug breakpoint silently wiped after saving modified function file

[Rik]

Update of bug #60889 (project octave):

                  Status:                    None => Need Info              

    _______________________________________________________

Follow-up Comment #1:

Breakpoints are supposed to be deleted when you modify an m-file.  Consider
the situation where you set a breakpoint at line 100.  Then you modify the
m-file, such that it no longer has 100 lines.  The breakpoint is now stale and
won't work.  Similarly, if you set a breakpoint at line 100 and then removed a
line the existing breakpoint would now point at the previous line 101 which is
not correct.  Octave's solution is too delete all breakpoints when an m-file
has been changed.

Now, if you use the GUI editor it keeps track of the breakpoints that are set
and after they have been cleared by the Octave interpreter it re-instates the
breakpoints in the newly saved file.

My guess is that the warning about the time stamp is significant.  Is the full
path to the m-file on an external, networked drive with a different time from
the machine where Octave is running?  What happens if you place the m-file on
your local hard drive?

I used the attached tst_bpoint.m for testing along with your intstructions and
it worked fine for me.

(file #51655)
    _______________________________________________________

Additional Item Attachment:

File name: tst_bpoint.m                   Size:0 KB
    <https://file.savannah.gnu.org/file/tst_bpoint.m?file_id=51655>



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?60889>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/