Re: Under what circumstances will catch (...) not catch?
Re: Under what circumstances will catch (...) not catch?
- Subject: Re: Under what circumstances will catch (...) not catch?
- From: David Rowland <email@hidden>
- Date: Wed, 28 Nov 2007 15:25:47 -0800
On Nov 28, 2007, at 3:16 PM, Larry Campbell wrote:
In a large project that worked well under Tiger and Xcode 2.4, I'm
having a bizarre problem with Leopard and Xcode 3.0. In the
following snippet:
bool failed = false;
try {
minfo.read(instr);
} catch (...) {
failed = true;
}
minfo.read() is expected to throw an exception, and it does, but the
runtime acts as though there's no handler in scope and calls
abort(), rather than letting my handler run.
How can this be?
any chance that some destructor which is called for a local var is
also throwing an exception?
_______________________________________________
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