[Top][All Lists]

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

[Octave-bug-tracker] [bug #46795] dbstop lacks much Matlab functionality

From: Lachlan Andrew
Subject: [Octave-bug-tracker] [bug #46795] dbstop lacks much Matlab functionality
Date: Fri, 15 Jan 2016 05:09:58 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:43.0) Gecko/20100101 Firefox/43.0

Follow-up Comment #28, bug #46795 (project octave):

I've briefly tested the new patch, Torsten, and it seems to work as intended.

You changed the colour of the conditional breakpoint marker.  Was there a
particular reason?  The reason I ask is that I'm thinking of making a new
marker class to mark the current line in the stack frame entered by "dbup" or
"dbdown".  I was thinking of making it either dark grey or greyish green.

The testing revealed an existing limitation: if there is a breakpoint in a
file, then opening the file doesn't load the breakpoints into the editor.  Dan
Sebald's original patch relied on patch #8016, which would allow the gui to
call "dbstatus" using signals.  Instead, I have written some code to query the
db_table data structure directly.

Since that new code isn't specific to the expanded dbstop, I've made a
separate patch [dbstop_20160115_after.cset], to be applied after your

(file #36041)

Additional Item Attachment:

File name: dbstop_20160115_after.cset     Size:3 KB


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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