[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #53064] "clear all" should not clear breakpoin
From: |
John W. Eaton |
Subject: |
[Octave-bug-tracker] [bug #53064] "clear all" should not clear breakpoints |
Date: |
Fri, 9 Feb 2018 11:51:17 -0500 (EST) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 |
Follow-up Comment #2, bug #53064 (project octave):
Currently, breakpoint lists are attached to the statement lists that are part
of the octave_user_script and octave_user_function objects. The destructors
for those classes clear the breakpoints.
It may be true that fixing this problem is as easy as the attached patch. But
are the breakpoints restored properly when the function is loaded again? I
haven't checked.
It may be time to take another look at the way breakpoints are handled. It
seems to me that they should be stored external to the parse tree object
instead of being attached to them, then used by the interpreter to decide when
to stop.
(file #43215)
_______________________________________________________
Additional Item Attachment:
File name: diffs.txt Size:0 KB
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?53064>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/