GCC 2.95.2 and exceptions
GCC 2.95.2 and exceptions
- Subject: GCC 2.95.2 and exceptions
- From: Bret Kurth <email@hidden>
- Date: Mon, 13 Sep 2004 13:08:40 -0500
I have an application project that is linking against a .a library from
an external vendor. Both projects are built with GCC 2.95.2 for 10.1
and later support. This is out of my hands and cannot change. The .a
lib is approximately 2.5MB and the application is also 2.5MB in size.
This is mostly code.
I'm running into a problem with exceptions and GCC 2.95.2.
Specifically, throws are not being caught, rather resulting in an
immediate call to __terminate(). If I switch to the 3.1 or later
compiler (merely for testing) the throws are caught by the first
catch() statement up the stack as expected.
I have dug through large volumes of information on the internet which
suggests this might be a bug in the GCC 2.95.2 compiler but I have
found nothing concrete. Has anyone else run into a similar problem?
If so, any work-arounds?
I have tried several suggestions in the MacOS X 10.1 Developer Tools
release notes related to the compiler flags -fno-eh-cleanup-section and
-fno-omit-frame-pointer without success. An additional comment was
made to remove all alloca() calls from the code but I found none in
either the library or the application.
Bret
_______________________________________________
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