• 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
Re: Debugging on Leopard
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Debugging on Leopard


  • Subject: Re: Debugging on Leopard
  • From: "Clark S. Cox III" <email@hidden>
  • Date: Tue, 13 Nov 2007 10:13:06 -0800


On Nov 13, 2007, at 08:45, Kenny Leung wrote:

Hi All.

Here's a tip that would have saved me a couple of days in debugging. Hopefully it will save somebody else some time.

I always have a breakpoint set on -[NSException raise] in order to trap any exceptions that get hit. On Tiger and previous this has never failed me, but on Leopard, not all exceptions go through - [NSException raise]. So during Leopard developement, some exceptions went unnoticed. It's safer if you also break on +[NSException raise:format] and objc_exception_throw. Hopefully there are no other paths through which an exception can be thrown.

All raised objective-C exceptions on Leopard go through objc_exception_throw, so no other breakpoint is needed.



-- Clark S. Cox III email@hidden

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

_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Debugging on Leopard (From: Kenny Leung <email@hidden>)

  • Prev by Date: Re: Test Cases + Nib files
  • Next by Date: Re: Leopard real amount of RAM used by application
  • Previous by thread: Debugging on Leopard
  • Next by thread: Re: Debugging on Leopard
  • Index(es):
    • Date
    • Thread