uncaught exception
uncaught exception
- Subject: uncaught exception
- From: Eric Slosser <email@hidden>
- Date: Wed, 7 Dec 2005 11:50:11 -0500
I've got an app and several private frameworks, built with several targets scattered amount a couple Xcode projects. Xcode 2.2, gcc 4.0.1.
When code in the framework throws an exception, e.g. "throw CMyException(err)", the catch handler on the app side doesn't get it, and it's treated like an uncaught exception and aborts the app.
???? #0 0x9004a12c in kill
#1 0x90120954 in abort
#2 0x9547deb4 in __gnu_cxx::__verbose_terminate_handler
#3 0x9547ba54 in __cxxabiv1::__terminate
#4 0x9547bab8 in std::terminate
#5 0x9547bd14 in __cxa_throw
I've confirmed that the framework is build with the -single_module flag, and that RTTI is turned on for all concerned.
I've confirmed (I think) that I'm not throwing an exception from a destructor, or anytime after __cxa_throw is first called with the exception that's going to be uncaught.
I can register a catch handler on the framework side, and it catches the exception. I can throw and catch an 'int' across the framework boundary.
I'm about to poke into the bowels of how exceptions and handlers are matched up. Despite my belief to lifelong learning, I'd just as soon have someone just tell me the answer. Anyone?
--
//-------------------------------------------------
email@hidden virtual-fx, inc. 617 314-9400
_______________________________________________
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