Re: C++ exception results in SIGABRT
Re: C++ exception results in SIGABRT
- Subject: Re: C++ exception results in SIGABRT
- From: Stefan Werner <email@hidden>
- Date: Tue, 19 Feb 2008 19:03:38 +0100
On Feb 19, 2008, at 5:55 PM, Alastair Houghton wrote:
It seems desirable to me (to *not* enable it, that is). C code
can't possibly handle a C++ exception, so throwing through a C
frame, unless it's one you have total control over, is a risky thing
to do. Even then, you have to be pretty careful not to e.g. leak
resources or leave the code in an invalid state. Better, therefore,
to generate SIGABRT unless the programmer has specifically said it's
OK by enabling -fexceptions, surely?
That I fully agree with. What's puzzling me is that checking "Enable C+
+ Exceptions" or respectively adding the equivalent line in my
xcconfig files did not result in -fexceptions being added to the gcc
command.
I ended up adding -fexceptions to OTHER_CFLAGS instead.
-Stefan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden