[Octave-bug-tracker] [bug #41338] dbstatus() doesn't return all breakpoints when called in a function

[Rik]

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:

  <http://savannah.gnu.org/bugs/?41338>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/