[Octave-bug-tracker] [bug #47585] GUI editor does not show already active breakpoints when a file is opened

[Philip Nienhuis]

Follow-up Comment #2, bug #47585 (project octave):

Maybe related, maybe also a little related to bug #33411, but I see the other
way round as well (when testing again for bug #33411) with the dev version:

function [ ret ] = foo ()
   printf ("Hello!\n");
endfunction


>> which foo
'foo' is a function from the file C:\Users\philip\MyDocs\octave\foo.m
>> edit foo.m      ## Appears in GUI editor
>> dbstop foo 2
ans =  2           ## breakpoint appears in GUI editor
>> foo
stopped in C:\Users\philip\MyDocs\octave\foo.m at line 2
2:    printf ("Hello!\n");
debug> dbcont
Hello!
>> run foo         ## This is bug 33411. Does not stop
>> dbclear foo
>> foo
Hello!
>>


but after the "dbclear foo" command the breakpoint is cleared (foo.m runs to
the end) but in the editor the breakpoint is still visible. It cannot be
cleared either (neither with "toggle breakpoints", "clear all breakpoints" or
clicking on it).
Only exiting the editor (or closing the foo.m editor tab) and reopening foo.m
in the editor helps.


    _______________________________________________________

Reply to this item at:

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

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