[Octave-bug-tracker] [bug #37576] Hitting CTRL+C with debug_on_error(1) does not go into debug mode, does in ML

[Richard]

URL:
  <http://savannah.gnu.org/bugs/?37576>

                 Summary: Hitting CTRL+C with debug_on_error(1) does not go
into debug mode, does in ML
                 Project: GNU Octave
            Submitted by: crobar
            Submitted on: Mon 15 Oct 2012 10:39:44 AM GMT
                Category: Interpreter
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Matlab Compatibility
                  Status: None
             Assigned to: None
         Originator Name: Richard Crozier
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: GNU/Linux

    _______________________________________________________

Details:

In matlab, when you hit CTRL+C with the equivalent of debug_on_error set to
true (in matlab this is set by "dbstop if error") matlab drops into debug mode
at the currently executing line.

In contrast Octave simply quits execution of whatever is currently running and
returns to the octave command prompt.

This functionality can be useful in various situation, e.g. locating endless
loops in code which does not always exhibit the behaviour, and tracking down
difficult to reproduce bugs, and examining the contents of variables when they
occur.




    _______________________________________________________

Reply to this item at:

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

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