[Octave-bug-tracker] [bug #35795] dbstep doesn't do single line stepping when error_status is set

[Jordi Gutiérrez Hermoso]

Follow-up Comment #2, bug #35795 (project octave):

I'm not sure this really is a bug. By the time an error has happened, Octave
may have encountered a state it can't recover from... yet you want to recover?
I find toggling debug_on_error to be a useful mechanism for figuring out what
was the state when the error happened, but not for stepping again. After all,
after the error happened, perhaps some variable was expected to be assigned to
the value after the error was caught, so what should the debugger do with that
variable?

After error status has been set, it seems to me like Octave can drop you into
that environment that caused the error, but then it has to rewind and dump you
back into the interpreter as soon as possible and get out of the error state
as soon as possible.

    _______________________________________________________

Reply to this item at:

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

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