http://bugs.winehq.org/show_bug.cgi?id=23868
Summary: C++: Exception is thrown but application is exited silently Product: Wine Version: 1.1.43 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: nil094@yahoo.com
Created an attachment (id=29969) --> (http://bugs.winehq.org/attachment.cgi?id=29969) exception code
When throwing an exception in C++, the application is supposed to abort, unless the exception had been catched. This is usually done inside blocks (functions, classmethods, etc).
The attached code throws an exception derived from std::runtime_error, causing the application to exit.
when running this on Linux, the output is similar to: terminate called after throwing an instance of 'Exception' what(): some awful error occured Aborted
and the errorcode ($?) is set to "134". However, when compiling the code with mingw and running it with wine, the application exists silently with no visible sign of a thrown exception; the only thing that indicates an error is the variable "$?" which is set to "3".
As I don't think this is expected behaviour, I have reported it as a Bug.
To compile "except.cpp", use this command: wine C:/MinGW/bin/g++.exe except.cpp -o except.exe
http://bugs.winehq.org/show_bug.cgi?id=23868
Sebastian nil094@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|C++: Exception is thrown |C++: Exception is thrown |but application is exited |but application exits |silently |silently
http://bugs.winehq.org/show_bug.cgi?id=23868
--- Comment #1 from Alexandre Julliard julliard@winehq.org 2010-08-02 02:58:37 --- Exit codes don't have the same meaning on Windows, an abort causes exit code 3. That is normal.
http://bugs.winehq.org/show_bug.cgi?id=23868
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #2 from Dmitry Timoshkov dmitry@codeweavers.com 2010-08-02 03:03:51 --- Invalid then.
http://bugs.winehq.org/show_bug.cgi?id=23868
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #3 from Dmitry Timoshkov dmitry@codeweavers.com 2010-08-02 03:04:00 --- Closing.
http://bugs.winehq.org/show_bug.cgi?id=23868
--- Comment #4 from Sebastian nil094@yahoo.com 2010-08-02 04:17:39 --- (In reply to comment #1)
Exit codes don't have the same meaning on Windows, an abort causes exit code 3. That is normal.
(In reply to comment #1)
Exit codes don't have the same meaning on Windows, an abort causes exit code 3. That is normal.
I wasn't complaining about the exit code. at all.
I was complaining about the lack of obvious evidence that an exception had been thrown; which does exist on windows XP (and up), where windows would abort the application with a messagebox saying something similar to: This application has been aborted in an unusual way
whereas wine does nothing. absolutely nothing. well, except just killing the application silently.
http://bugs.winehq.org/show_bug.cgi?id=23868
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |UNCONFIRMED Resolution|INVALID |
--- Comment #5 from Alexandre Julliard julliard@winehq.org 2010-08-02 04:46:06 --- Why did you bring up the behavior on Linux then? Certainly you don't get a message box there. But yes, to behave like Windows we could put one up at that point.
http://bugs.winehq.org/show_bug.cgi?id=23868
--- Comment #6 from Sebastian nil094@yahoo.com 2010-08-02 05:55:33 --- (In reply to comment #5)
Why did you bring up the behavior on Linux then? Certainly you don't get a message box there.
That was merely an example.
But yes, to behave like Windows we could put one up at that point.
I'm not saying that wine should copy the exact behaviour; but sort of a "notification" would be useful in some places.
http://bugs.winehq.org/show_bug.cgi?id=23868
--- Comment #7 from butraxz@gmail.com 2013-06-09 11:35:40 CDT --- This has not been updated for over 900 days.
Is this still an issue in 1.6-rc1 or higher or is this abandoned ?
http://bugs.winehq.org/show_bug.cgi?id=23868
--- Comment #8 from Sebastian nil094@yahoo.com 2013-06-09 12:17:15 CDT --- (In reply to comment #7)
This has not been updated for over 900 days.
Is this still an issue in 1.6-rc1 or higher or is this abandoned ?
It has been closed as wontfix (well, unofficially, that is). The spectrum that would require special behaviour is much broader than I considered at the time I opened this bug, and needless to say, it's not as easy to implement as I thought.
https://bugs.winehq.org/show_bug.cgi?id=23868
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX
--- Comment #9 from Austin English austinenglish@gmail.com --- WONTFIX.
https://bugs.winehq.org/show_bug.cgi?id=23868
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #10 from Austin English austinenglish@gmail.com --- Closing.
-
wine-bugs＠winehq.org