Just a quick one: This may be obvious to many devs, but it’s worth noting. One common and useful debugging technique is breaking on exceptions, so that you can see exactly where in your app’s flow a breakpoint occurs.

This can be done by adding -[NSException raise] and objc_exception_throw to your breakpoints list.

Once an exception happens, you can then check out the exception itself to see what went wrong. The approach varies between platforms. If you’re in the simulator (or any Mac OS X app running on Intel), the exception will be stored in the $eax register. Take a look by typing:

po $eax

If you’re on the iPhone, it’ll be $r0, so:

po $r0

Related posts

• Getting Data out of the iPhone while Debugging Here’s a utility I whipped up quickly to save out...
• iPhone/Mac animation for custom classes: Property animation for more than just CALayer An Objective-C class that provides similar functionality to CABasicAnimation, but...
• Breaking the limits: Storing data bigger than 1 Mb in Google App Engine’s Datastore Google App Engine is a fantastic platform for hosting webapps,...