[Octave-bug-tracker] [bug #47605] dbwhere hangs after debug_on_error stops Octave

[Dan Sebald]

Follow-up Comment #9, bug #47605 (project octave):

That's right, the last sentence isn't quite how that works.  The curr_frame is
initialized to NULL when the class object is constructed.

I looked at the cs[] layout last night but didn't quite understand the
indexing.  FWIW, in toplevel.h the "curr_frame > 1" could be "curr_frame > 0"
in the following:


  octave_function *do_caller (void) const
  {
    return curr_frame > 1 ? cs[curr_frame-1].m_fcn : cs[0].m_fcn;
  }


Not that it matters, just that the frame of reference of greater than zero
might be more how curr_frame is defined.

    _______________________________________________________

Reply to this item at:

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

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