[Top][All Lists]

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

[Octave-bug-tracker] [bug #41338] dbstatus() doesn't return all breakpoi

From: Rik
Subject: [Octave-bug-tracker] [bug #41338] dbstatus() doesn't return all breakpoints when called in a function
Date: Fri, 24 Jan 2014 18:59:27 +0000
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0

Update of bug #41338 (project octave):

                  Status:                    None => Confirmed              


Follow-up Comment #1:

The issue is that Octave is trying to be "helpful" about what breakpoints it
shows.  When you are debugging a function, and in a function context, dbstatus
gives you the list of breakpoints in the current function.  In the same way,
calling dbclear while inside a debugging context will clear the breakpoints
for the current file.

Lots of room for improvement here.  It seems like an easy one would be only
have the special behavior for dbstatus when actually in debugging mode.  The
attached patch seems to work for me.

I think these internal changes probably need to go on to the development
branch rather than the 3.8.X branch since they would change behavior that some
coders may have come to rely on.

(file #30364)

Additional Item Attachment:

File name: patch.dbstatus                 Size:0 KB


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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