Thu 31 Mar 2016 03:28:27 PM UTC, comment #9:
Ok, thanks, closing as fixed. I see the same behavior you report in comment #8 on Debian, I'll report that if there's not already one about that.
|
Thu 31 Mar 2016 03:21:01 PM UTC, comment #8:
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:
- 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).
|
Wed 30 Mar 2016 10:02:45 PM UTC, comment #7:
Mike, I wanted to test today (built with this patch yesterday) but I ran in zip/gzip issues (see bug tracker).
Hopefully I have more time tomorrow.
|
Wed 30 Mar 2016 06:25:32 PM UTC, comment #6:
Still awaiting testing and confirmation of the fix on the default branch on Windows.
|
Thu 25 Feb 2016 09:10:40 AM UTC, comment #5:
Nicholas and Harry, can you say whether this still happens after changeset
http://hg.savannah.gnu.org/hgweb/octave/rev/0a09c3cae800
eight weeks ago?
|
Mon 27 Jul 2015 12:25:16 AM UTC, comment #4:
and another one.
went to add a breakpoint, had a parentheses mismatch syntax error and got the error :
again, a breakpoint appeared at the line I selected, but I can't deselect it. In addition, the yellow 'step' marker is also showing a few lines below that for no apparent reason since I haven't entered debugging mode yet.
|
Sun 26 Jul 2015 01:39:28 AM UTC, comment #3:
just one example from today:
I was editing a function, and had changed the name of the function but forgot to change the name of the file to match. I clicked to add a breakpoint to run a test, and the command window gave me the warning about the filename not matching the function name. I edited the function name to match again just so it wouldn't give me the warning, and noticed the breakpoint was set where I had clicked, but clicking it again it wouldn't clear. It's been there now through several rounds of debugging. expect it will stay until I close the file.
|
Fri 24 Jul 2015 08:09:43 PM UTC, comment #2:
I can confirm seeing this on Windows. I haven't been able to figure out what creates a 'phantom' breakpoint, but it will stay in the editor until that file is closed/reopened. Other times the behavior is as expected, and the red breakpoints are created & cleared as you'd expect. So, something happens during debugging to make it lose track of the red circle.
Next time I debug I'll try to pay attention to what I'm doing and if it occurs.
|
Fri 26 Jun 2015 06:18:42 PM UTC, comment #1:
Works for me in 4.0.0 on GNU/Linux. Is anyone else able to reproduce this in Windows?
|
Wed 24 Jun 2015 06:46:35 PM UTC, original submission:
The breakpoint images are not refreshed after the clear all the breakpoints icon is pressed. While it is done in terms of the code, the visual information is the same as if the person did not refresh this.
|