[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #55178] Improved debug on error behaviour insi

From: Georg Wiora
Subject: [Octave-bug-tracker] [bug #55178] Improved debug on error behaviour inside octave core functions
Date: Fri, 7 Dec 2018 05:11:47 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:63.0) Gecko/20100101 Firefox/63.0


                 Summary: Improved debug on error behaviour inside octave core
                 Project: GNU Octave
            Submitted by: gwiora
            Submitted on: Fri 07 Dec 2018 11:11:45 AM CET
                Category: Octave Function
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Feature Request
                  Status: None
             Assigned to: None
         Originator Name: gwiora
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 4.4.1
        Operating System: Any



*Feature request*

I recommend changing the behavior of the debug_on_error() method inside
octaves core functions in a way similar to matlab.

When debug_on_error is activated in matlab and an error appears inside a core
function, the debugger stops at the calling function in the user code. In the
same situation Octave stops inside the core function even when the core
function calls error() to produce a message. This is very annoying during
debugging user functions. I like to have debug_on_error() activated
permanently, because it is so useful.

Currently the side effect of activating debug_on_error is, that every syntax
error and wrong command causes the "print_usage" function to be opened in the
editor and debugger is stopping there. This is not what I need as octave

*Suggested solution*

Every core function (and probably as a recommendation also packet functions)
should have as first command:

  # enable return to caller on error
  return_and_stop_on_error (true);

This should remove the top stack frame and stop the debugger in the callers
function at least when the called function actively issues an error().

There could be an additional global signal to enable core function debugging.


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]