- Git - Basic Terminal Commands Checklist wp.me/pCBOm-9U via @wordpressdotcom 18 hours ago
- RT @doougle: "Ultimate Tic-Tac-Toe" - one of the cleverest bits of game design I've seen in a while: bit.ly/169WB3w (via @blackmad) 1 day ago
- RT @gregmaletic: First thought upon using an iPhone: this is a computer so easy my mom could use it. First thought using iOS 7: this will t… 1 day ago
- RT @anrickbregman: If you're doing, you're doing fine. Don't worry about the competition, it's not a race. Just make something beautiful, m… 2 days ago
- Sat down to create Node.js sample app.. end up processing portland trip photo from My Labs 500px.com/photo/37716316 3 days ago
Just another iPhone Blog
Capturing Exceptions while debugging
February 23, 2012Posted by on
This one is a simple but could be time-saving
Scenario: If you are debugging and caught with awkward situation where the application crashes with an exception, like NSInvalidArgumentException and so on, but never take you to the place in the code where the problem exists.
Remember, This solution is for Xcode 4.2.1 for Lion.
1. Select View->Navigators->Show Breakpoint Navigator
2. At the Bottom-left cornet, Click the ‘+’ symbol and Select ‘Add Exception Breakpoint’ Menu
3. In the popped-up window you may select [All | Objective-C | C++ ] options to select what type of Exception should the execution stop.
4. Click Done.
Restart your debug process and you should see the line of code that is causing the hassle for you
Courtesy: Apple Developer Document.