On Tue, Feb 23, 2016 at 15:07:10 -0500, John W. Eaton wrote:
On 02/23/2016 12:26 PM, Rik wrote:
The other command that I find more useful, so useful in fact that I
copied it from gdb and implemented it in Octave, is dblist. It shows
the code immediately around where the debugger is stopped. It is less
cumbersome than having to enter a RANGE into dbtype.
But, to your point, the debugger would be more useful if it followed
where you were in the stack. Can you file a bug report on Savannah
about that?
I checked in the following changeset:
http://hg.savannah.gnu.org/hgweb/octave/rev/909129eb77c5
It seems to work more like I would expect now.
This changeset causes some tests to turn into infinite loops. I bisected
to verify this was the cause of what I'm seeing. The first test when
running "make check" hangs.