bugGNU Octave - Bugs: bug #54454, Calling mexErrMsgTxt with message...

 
 

bug #54454: Calling mexErrMsgTxt with message ending in "\n" should suppress backtrace

Submitted by:  Rik <rik5>
Submitted on:  Mon 06 Aug 2018 04:42:20 PM UTC  
 
Category:  Interpreter Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Feature Request
Status:  Fixed Assigned to:  None
Originator Name:  Open/Closed:  Closed
Release:  dev Operating System:  Any

Add a New Comment (Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Wed 08 Aug 2018 05:13:54 AM UTC, comment #1: 
Rik <rik5>
Project Administrator
Mon 06 Aug 2018 04:42:20 PM UTC, original submission:  

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.

Rik <rik5>
Project Administrator

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

Attached Files
file #44732:  mexbacktrace.tgz added by rik5 (2KiB - application/x-compressed-tar)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by rik5 (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only project members can vote.

     

     

     

    Follow 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2018-08-08 rik5 StatusConfirmed => Fixed
        Open/ClosedOpen => Closed
    2018-08-06 rik5 Attached File- => Added mexbacktrace.tgz, #44732

    Back to the top


    Powered by Savane 3.5