[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #55456] "dbstop if all error" support
|
From: |
Andrew Janke |
|
Subject: |
[Octave-bug-tracker] [bug #55456] "dbstop if all error" support |
|
Date: |
Sat, 12 Jan 2019 04:44:53 -0500 (EST) |
|
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 |
Follow-up Comment #2, bug #55456 (project octave):
I'm afraid not. After doing 'debug_on_error(true)', when an error is raised
inside a try/catch block like this:
try
... some code ...
... error() happens in a function call in here ...
... some more code ...
catch err
error('Something bad happened: %s', err.message);
end
the breakpoint is hit at the error() inside the catch block, not the original
error. This seems like the same behavior as plain "dbstop if error", not
"dbstop if all error".
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?55456>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/