22

I use NSSetUncaughtExceptionHandler to print the stack trace to local file in iPhone, which will be sent to our server next time the app launches. Then I can examine the exception data and fix the bug. In some crashes I have the module name and the function that threw the exception, these are easy. But mostly I have something like this:

"4   libc++abi.dylib 0x35bba3c5 _ZL19safe_handler_callerPFvvE + 76",
"5   libc++abi.dylib 0x35bba451 _ZdlPv + 0",
"6   libc++abi.dylib 0x35bbb825 __cxa_current_exception_type + 0",
"7   libobjc.A.dylib 0x37bab2a9 objc_exception_rethrow + 12",
"8   CoreFoundation  0x3575a50d CFRunLoopRunSpecific + 404"

and for example the reason:

*** -[__NSArrayI objectAtIndex:]: index 0 beyond bounds for empty array

but I have dozens of arrays in my app, so I need help to find the specific line that threw the exception, using the data I get from the stack trace.

Does anyone know a good article/tutorial from Apple or other, where I can learn to decode the numbers in the stack trace to find the problematic line in the source code. Thanks in advance!

Ankur
  • 5,086
  • 19
  • 37
  • 62
Lena Grushevsky
  • 416
  • 5
  • 8
  • 9
    I suggest you to read this tutorial [`My App Crashed`](http://www.raywenderlich.com/10209/my-app-crashed-now-what-part-1) – Sumanth Aug 27 '12 at 12:19
  • 4
    This is a post I wrote that uses atos to translate. I rarely use this method anymore since now I just copy the crash log into Xcode Organizer which does the symbolication quite nicely. Anyways, it may help: http://saveme-dot-txt.blogspot.com/2011/04/using-atos-for-reading-crash-logs.html – Mike M Aug 27 '12 at 12:34
  • Maybe does GTMStackTrace help http://code.google.com/p/google-toolbox-for-mac/source/browse/trunk/Foundation/GTMStackTraceTest.m?r=495 – zeiteisen Aug 27 '12 at 13:17
  • 2
    Mike M, what do you mean you copy the crash log into XCode Organizer? – Lena Grushevsky Aug 27 '12 at 17:02
  • This link shows how to use lldb's `image lookup` and `source list` To find the offending line of code: http://stackoverflow.com/questions/18112842/how-can-i-find-the-address-of-a-stack-trace-in-lldb-for-ios – Rob Nov 30 '14 at 13:50

4 Answers4

24

I strongly recommend enabling Exception Breakpoint in Xcode. It will stop execution of your code on the exact line which crashes your application. So you do not need to worry about which of the array cause of the crash. *** -[__NSArrayI objectAtIndex:]: index 0 beyond bounds for empty array

Adding exception breakpoint

  1. Go to Breakpoints section on Xcode
  2. Click on plus sing at bottom of the section
  3. Select Add Exception Breakpoint

Exception BreakPoint

bpolat
  • 3,879
  • 20
  • 26
  • 1
    I believe the OP was looking to find the line number from a stack trace sent as a crash report to a server/database, i.e. she is not testing in XCode and does not have access to its breakpoint resources. – dcgoss Mar 04 '15 at 15:34
2

I don't know how to get line numbers from stack traces (yet), but at some points in my code where I want to get line number printed I used the have the following code fragment:

NSLog(@"%s line=%d", __func__, __LINE__);

which will give the following output:

2013-04-01 00:16:46.393 MyApp[847:c07] -[AppDelegate application:didFinishLaunchingWithOptions:] line=29

If you're familiar with the Log4J framework I'ld suggest to take a look at the Lumberjack framework which proves to be very helpful for me in various projects.

https://github.com/robbiehanson/CocoaLumberjack

Although this may not directly answer your question, its just meant as a reminder.

iOS-Coder
  • 1,221
  • 1
  • 16
  • 28
-1

Set a breakpoint in the catch block, once the flow of code stops you can use gdb commands like 'bt'.

Ramy Al Zuhouri
  • 21,580
  • 26
  • 105
  • 187
-1

Print the stack trace stored in the exception, i.e. [exception callStackSymbols] or [exception callStackReturnAddresses]. In Apple's crash logs since iOS 5, this shows up at the top as "Last Exception Backtrace".

What you're seeing is the call stack when the exception is re-thrown, which will happen for things as simple as try...finally. I'm not sure exactly why Apple made this change (possibly to make run loops exception-safe?), but there you go.

tc.
  • 33,468
  • 5
  • 78
  • 96