While debugging is there anyway to see a complete stack trace, list of methods called in main thread. Or any way to print them on command window.
Use the bt command in (lldb). Once paused or after a crash, just type bt into the debug console. It will print the full stack trace. Awesome tip for tracking down a constraint issue after setting the symbolic breakpoint.
In computing, a stack trace (also called stack backtrace or stack traceback) is a report of the active stack frames at a certain point in time during the execution of a program.
In Objective-C, you can print the call stack by doing the following: NSLog(@"%@", [NSThread callStackSymbols]);
Use the bt
command in (lldb).
Once paused or after a crash, just type bt
into the debug console.
It will print the full stack trace.
You can print the stack trace in the NSLog by
NSLog(@"Stack trace : %@",[NSThread callStackSymbols]);
Upon a crash, next to the word (lldb)
, you can type:
po [NSThread callStackSymbols]
Edit:
For better output on console on Swift you can use following line instead:
Thread.callStackSymbols.forEach{print($0)}
In Xcode 6 you can click the button at the bottom left corner of the pane which shows the full stack trace.
In Xcode 5 you can move the slider at the bottom of the pane which shows the stack trace. It controls how much of the struck trace is shown.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With