|
From: | Rik |
Subject: | [Octave-bug-tracker] [bug #54454] Calling mexErrMsgTxt with message ending in "\n" should suppress backtrace |
Date: | Mon, 6 Aug 2018 12:42:22 -0400 (EDT) |
User-agent: | Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:61.0) Gecko/20100101 Firefox/61.0 |
URL: <http://savannah.gnu.org/bugs/?54454> Summary: Calling mexErrMsgTxt with message ending in "\n" should suppress backtrace Project: GNU Octave Submitted by: rik5 Submitted on: Mon 06 Aug 2018 09:42:20 AM PDT Category: Interpreter Severity: 3 - Normal Priority: 5 - Normal Item Group: Feature Request Status: Confirmed Assigned to: None Originator Name: Originator Email: Open/Closed: Open Discussion Lock: Any Release: dev Operating System: Any _______________________________________________________ Details: When Octave's error() function is called with an error message that ends in a newline, the backtrace from the interpreter is suppressed. It would be nice to have consistency with the mex interface so that a mex function error message that ends in a newline *also* suppresses the backtrace in the interpreter. I've attached a test case. See the README file on how to invoke it. _______________________________________________________ File Attachments: ------------------------------------------------------- Date: Mon 06 Aug 2018 09:42:20 AM PDT Name: mexbacktrace.tgz Size: 2KiB By: rik5 <http://savannah.gnu.org/bugs/download.php?file_id=44732> _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?54454> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |