[Octave-bug-tracker] [bug #45397] BreakPoints not visually clearing after GUI clear all breakpoints has been clicked

[Philip Nienhuis]

Follow-up Comment #8, bug #45397 (project octave):

With the patch:

As to comment #4, I cannot enter breakpoints unless the file is
syntax-error-free; after fixing the syntax and saving (!) the breakpoint
appears.

The "Clear all breakpoints" button works fine AFAICS.

Pressing the "Toggle breakpoints" button now works (AFAICS!) more reliably
than it used to be. What still happens is this:
- create a function tstdbg:

function [retval] = tstdbg (input1)
  if (! isempty (input1))
    retval = 2
  endif
endfunction


- enter a breakpoint at L. 2 (the "if" stmt)
- close the editor tab (or editor) with the file, editor pane = empty
- run the command "tstdbg (1)"
- the file pops up in the editor interrupted on L.2, with the yellow
instruction/poistion marker at L. 2, but without breakpoint marker.
So the behavior is correct, but the breakpoint marker is missing.

Moreover, once in the popped up editor (pane), clicking the "toggle
breakpoint" button makes the breakpoint marker appear. The breakpoint is still
active then.
Only clicking the button a second time makes it disappear, and after clicking
away and running "tstdbg (4)" the breakpoint seems to have been finally
removed (dbclear-ed).


    _______________________________________________________

Reply to this item at:

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

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