[Octave-bug-tracker] [bug #44862] Errors in script files don't generate tracebacks

[Martin Kunz]

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

                 Summary: Errors in script files don't generate tracebacks
                 Project: GNU Octave
            Submitted by: mkunz
            Submitted on: Fr 17 Apr 2015 14:14:46 GMT
                Category: Interpreter
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Regression
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 4.0.0-rc3
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

Octave 4.0.0-rc3 prints no traceback messages when an error occurs in a script
file. Consider a simple testScript.m with the following content:

a=1;
a(2);

When I run this script with Octave 3.8.2 I get:

 >> testScript
error: testScript: A(I): index out of bounds; value 2 out of bound 1
error: called from:
error:   D:\scripting\octave\octaveScripts\testScript.m at line 2, column 1

However, Octave 4.0.0-rc3 prints:

 >> testScript
error: testScript: A(I): index out of bounds; value 2 out of bound 1

and no traceback.

Executing the same two lines inside a function in Octave 4.0.0-rc3 produces an
error WITH traceback.

While one can use the lasterror function (thanks to Mike Miller for pointing
this out) to get all relevant info, I would strongly vote for restoring the
behaviour of Octave 3.8 where errors in script files are printed with
traceback per default.

I used http://alpha.gnu.org/gnu/octave/octave-4.0.0-rc3-installer.exe to get
Octave.




    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Nachricht gesendet von/durch Savannah
  http://savannah.gnu.org/