[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #46928] [debug mode] [GUI] fails to reset brea
|
From: |
Lachlan Andrew |
|
Subject: |
[Octave-bug-tracker] [bug #46928] [debug mode] [GUI] fails to reset breakpoint after error occurs |
|
Date: |
Tue, 19 Jan 2016 00:04:06 +0000 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:43.0) Gecko/20100101 Firefox/43.0 |
Follow-up Comment #1, bug #46928 (project octave):
The behaviour has changed since 4.0.0, especially with changeset 0a09c3cae800,
but this script is still problematic.
Now, the "clear all" clears the breakpoints but does not update the GUI's
markers for them, and they cannot be removed by clicking on the marker. (For
some reason, it sill stops at a breakpoint after the clear all, even though
dbstatus shows that breakpoint not being present.)
Once bug #46795 has been fixed to allow dbstop(s) for a structure s, I
plan to write a patch to restore all breakpoints after clear all or clear -f.
Does that sound a reasonable approach? The alternative is to cause the
symbols to be removed after clear all or clear -f
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?46928>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/