[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #46608] error() always prints backtrace
From: |
Rik |
Subject: |
[Octave-bug-tracker] [bug #46608] error() always prints backtrace |
Date: |
Sat, 05 Dec 2015 01:15:24 +0000 |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:42.0) Gecko/20100101 Firefox/42.0 |
URL:
<http://savannah.gnu.org/bugs/?46608>
Summary: error() always prints backtrace
Project: GNU Octave
Submitted by: rik5
Submitted on: Fri 04 Dec 2015 05:15:22 PM PST
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: dev
Operating System: Any
_______________________________________________________
Details:
In 4.0.0, the backtrace from an error could be disabled by ending the error
message with a newline. That is no longer possible in the development version
of Octave and the documentation for error() and warning() should be updated.
However, there is a new mechanism to disable backtraces.
warning ("off", "backtrace");
Unfortunately, this seems to be inoperative.
With the following function tst_err.m,
function [retval] = tst_err (x, y)
error ("Format string ending in newline\n");
endfunction
the sample session is
octave:1> diary on
octave:2> warning ("off", "backtrace")
octave:3> tst_err
error: Format string ending in newline
error: called from
tst_err at line 2 column 3
octave:3> diary off
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?46608>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #46608] error() always prints backtrace,
Rik <=