|
| From: | Rik |
| Subject: | [Octave-bug-tracker] [bug #52750] Ctl-C stops debugging when used only to stop long output when more off |
| Date: | Fri, 12 Jan 2018 20:16:09 -0500 (EST) |
| User-agent: | Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0 |
Follow-up Comment #10, bug #52750 (project octave):
This seems real. The patch for this was in pt-eval.cc and in the function
visit_statement.
catch (const octave::interrupt_exception&)
{
// If we are debugging, then continue with next statement.
// Otherwise, jump out of here.
if (debug_mode)
interpreter::recover_from_exception ();
else
throw;
}
But the dbquit function makes use of exceptions to return to the prompt.
{
if (! Vdebugging)
error ("dbquit: can only be called in debug mode");
if (args.length () != 0)
print_usage ();
Vdebugging = false;
octave::tree_evaluator::reset_debug_state ();
octave_throw_interrupt_exception ();
return ovl ();
}
Maybe reset_debug_state isn't resetting the state?
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?52750>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
| [Prev in Thread] | Current Thread | [Next in Thread] |