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

[Philip Nienhuis]

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

Thanks for this patch; I have just played a little bit with it.

While I am not very familiar with debug, most of the new functionality works
fine AFAICS. 
I'm not aware of any scoping rules for dbstop like e.g., debug_on_error has
("local" argument) but I've never experimented with it.

I tried the form "dbstop in <function> if (condition)". That form only seems
to work if the condition can be evaluated at the first statement of the
function, i.e., if the variable referenced in (condition) already exists upon
function entry. That can only be done for "variables" nargin and nargout.
It would be easier to understand for users if the evaluator can wait until the
variable comes into existence. But undoubtedly I am expecting too much :-) 
Matlab behaves the same after all.


A little annoying is that when clicking in the left column to set a
breakpoint, the editor contents scroll up or down so that the new breakpoint
is vertically "centered".

This new behavior resembles a little gripe of me with the current editor
behavior: when stepping through a debugged m-function, the current line is
always exactly vertically centered. 
I rather wish the file contents would stay in place as much as possible and
only scroll up when the "current line" (or "instruction pointer" if you wish)
gets to be 3 or 4 lines above the bottom (above editor status bar) and when
jumping backwards (while/for/do-until loops) scrolls down so that the current
line is 3-4 lines below the top (below editor menu bar).

Should I enter a separate bug report on this, or can it be mended while you
are at it?


    _______________________________________________________

Reply to this item at:

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

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