• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Under what circumstances will catch (...) not catch?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Under what circumstances will catch (...) not catch?


  • Subject: Under what circumstances will catch (...) not catch?
  • From: Larry Campbell <email@hidden>
  • Date: Wed, 28 Nov 2007 18:16:06 -0500

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?

- lc

Attachment: smime.p7s
Description: S/MIME cryptographic signature

 _______________________________________________
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

  • Follow-Ups:
    • Re: Under what circumstances will catch (...) not catch?
      • From: David Rowland <email@hidden>
  • Prev by Date: Re: 10.2.8 and leopard
  • Next by Date: Re: Under what circumstances will catch (...) not catch?
  • Previous by thread: App leaks file descriptors, but not when running via XCode
  • Next by thread: Re: Under what circumstances will catch (...) not catch?
  • Index(es):
    • Date
    • Thread