|
From: | Lachlan Andrew |
Subject: | [Octave-bug-tracker] [bug #47675] Breakpoint conditions get corrupted when edited in the GUI |
Date: | Wed, 13 Apr 2016 10:05:41 +0000 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:43.0) Gecko/20100101 Firefox/43.0 |
Follow-up Comment #1, bug #47675 (project octave): I forgot to mention how to replicate this error. Create the file tmp.m containing a = 1; b = 2; c = 3; Type dbstop in tmp at 1 if 1 dbstop in tmp at 2 if 2 dbstop in tmp at 3 if 3 Right click on line 1, and change the condition to '4'. Save the file twice (don't ask me why...), and then observe that dbstatus gives breakpoint in fred at line 1 if 4 breakpoint in fred at line 2 if 4 breakpoint in fred at line 3 if 3 even though the breakpoint at line 2 was not explicitly changed. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?47675> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |