[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Uninformative stack traces
From: |
John W. Eaton |
Subject: |
Uninformative stack traces |
Date: |
Thu, 27 Mar 2008 17:18:47 -0400 |
On 27-Mar-2008, Moritz Borgmann wrote:
| However, Octave outputs:
|
| ===
| octave:1> test_error
| error: Failure!
| error: evaluating if command near line 10, column 1
| error: called from `do_fail' in file `..../test_error.m'
| error: called from `test_error' in file `..../test_error.m'
| ===
|
| Here, it is impossible to tell whether the error was triggered by the
| calls on line 3, 4, or 5. This makes debugging quite hard in many
| cases. Is this a known problem? Or am I possibly even overlooking a
| simple fix, like some Octave configuration?
|
| OTOH, is it necessary to log all control structures in the stack
| trace, wouldn't the function calls suffice?
See
http://www.nabble.com/goals-for-3.1-to13732816.html#a14442472
item 6.
jwe