[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #44195] segfault with dbstatus

From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #44195] segfault with dbstatus
Date: Fri, 06 Feb 2015 11:21:10 +0000
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:33.0) Gecko/20100101 Firefox/33.0 SeaMonkey/2.30

Follow-up Comment #1, bug #44195 (project octave):

FTR, tried this under Windows with a (cross-)built 3.9.0+ and 4.1.0+ (before
the merges of gui-release & default into 3.9.0+) from January 26, and a 3.9.0+
(new default branch) from Feb 1.

I did as you outlined and then all three gave:

>> edit junk.m
>> dbstop ("junk", 2)
ans =  2
>> dbstop ("junk", 4)
ans =  4
## Now, just changing 1 -> 1A
>> dbstatus
breakpoint in junk at lines 2, 4.
## Now clicked "Save file"
>> dbstatus
## Breakpoints were wiped after saving the file, upon "dbstatus" cmd

so no problems there.

That said, the breakpoint bookkeeping in the editor might be less robust than
desired; I've filed another bug report (#44163) about some -perhaps related-
issues that do occur on Windows.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]