|
From: | Rik |
Subject: | [Octave-bug-tracker] [bug #50198] Calling "error" from the GUI thread lead to segfaults |
Date: | Wed, 31 Jan 2018 01:29:38 -0500 (EST) |
User-agent: | Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0 |
Update of bug #50198 (project octave): Status: None => In Progress _______________________________________________________ Follow-up Comment #7: The exception pointer could be const or not. There are several Stack Overflow articles on not treating pointer as const and modifying it. See https://stackoverflow.com/questions/8481147/if-you-catch-an-exception-by-reference-can-you-modify-it-and-rethrow#8481171 https://stackoverflow.com/questions/30580128/may-i-modify-the-value-of-an-exception-inside-a-stdexception-ptr I suppose one thing to consider is whether we are happy with the phrase "parse error" when something goes wrong with printing. Wouldn't it actually be nice to modify the message to be more accurate? _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?50198> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |