[Octave-bug-tracker] [bug #52750] Ctl-C stops debugging when used only to stop long output when more off

[Rik]

Follow-up Comment #11, bug #52750 (project octave):

Just to track what is going on I added 


+    std::cerr << "debug_mode: " << debug_mode << std::endl;


in to reset_debug_state().  First, it is getting called for every single
function evaluation which seems excessive.  I thought reset_debug_state()
would only be called when there had been a change to the debug state such as
adding a breakpoint or using dbquit.  Sample session below.


octave:2> x = 1
debug_mode: 0
x =  1
octave:3> y = 2
debug_mode: 0
y =  2
octave:4> x + y
debug_mode: 0
ans =  3


And as expected, the problem is that debug_mode is not reset because there are
still breakpoints outstanding.


octave:1> diary on
debug_mode: 0
octave:2> dbstop sind
debug_mode: 1
ans =  31
octave:3> sind (1)
stopped in /home/rik/wip/Projects_Mine/octave-dbg/scripts/elfun/sind.m at line
31
31:   if (nargin != 1)
debug> dbnext
stopped in /home/rik/wip/Projects_Mine/octave-dbg/scripts/elfun/sind.m at line
35
35:   I = x / 180;
debug> dbquit
debug_mode: 1

recovering
debug_mode: 1
ans =  0.017452




    _______________________________________________________

Reply to this item at:

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

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