Xcode full stack trace

Question

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.

possible duplicate of [Objective C - getting line number or full stack trace from debugger error?](http://stackoverflow.com/questions/10501358/objective-c-getting-line-number-or-full-stack-trace-from-debugger-error) — Mike Weller, Apr 11 '13 at 10:40
Programmatically, you can use callStackSymbols as Mihir describes. But of course you can also stop in Xcode, at a breakpoint (or just pressing "pause") and examine the stack in the left-hand column. (Always enable an exception breakpoint.) — Hot Licks, Apr 11 '13 at 10:47
(+1 for realizing that examining the stack is important. Far too few folks starting out on Xcode appreciate this.) — Hot Licks, Apr 11 '13 at 10:49
I am doing same, but in stack trace I can see just 5 or 6 method calls and after that on 25 its UIApplicationMain and on 26 its main. I can't see the methods between 6 and 25. I want to see complete stack trace. — NaXir, Apr 11 '13 at 11:00

score 164 · Answer 1 · edited Mar 15 '17 at 03:31

164

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.

sample output of bt command

edited Mar 15 '17 at 03:31

Pang

9,564
146
81
122

answered Nov 06 '14 at 02:47

Alex Iceman

1,679
1
11
6

Awesome tip for tracking down a constraint issue after setting the symbolic breakpoint. – Alex Walczak Feb 22 '20 at 00:12
1

You can also mention the thread id (from the debug pane) for capturing stack of that particular thread. For example, in case of Thread 42, you'd do - "bt 42" – rivaldo4t May 08 '20 at 22:25
Be patient as it took about 30 seconds for it to print out – abc123 Feb 02 '21 at 16:51

score 88 · Accepted Answer · edited May 15 '20 at 22:59

88

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)}

edited May 15 '20 at 22:59

jvarela

3,744
1
22
43

answered Apr 11 '13 at 10:33

Mihir Mehta

13,743
3
64
88

11

within lldb it can be printed with: po [NSThread callStackSymbols] – Max MacLeod Apr 23 '14 at 08:32
Updated the answer – Mihir Mehta Oct 26 '17 at 11:39
po Thread.callStackSymbols returns `cannot use dot operator on a type` – pho_pho Sep 04 '18 at 12:51

score 72 · Answer 3 · answered Oct 13 '14 at 13:33

72

In Xcode 6 you can click the button at the bottom left corner of the pane which shows the full stack trace. Xcode 6 show full stack trace

answered Oct 13 '14 at 13:33

Gong Pengjun

971
7
14

1

This answer is still current in Xcode 11, but the button has been moved slightly. ;) – ReinstateMonica3167040 May 15 '20 at 15:14

score 17 · Answer 4 · answered Oct 19 '13 at 09:29

17

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.

Slider controlling the stack trace

answered Oct 19 '13 at 09:29

Sergey A. Novitsky

455
6
9

6

How do you do this in Xcode 6? There is no slider anymore. – progrmr Oct 10 '14 at 21:22
3

This slider appears to have been removed in XCode6... if anyone knows how to do this under XCode6 you would be my hero. – Steazy Oct 21 '14 at 18:07
@Steazy See Gong Pengjun's answer for Xcode 6-11 (or possibly later, 11.x is current at this moment) – ReinstateMonica3167040 May 16 '20 at 00:51

Buntylm · Answer 5 · 2014-05-18T04:16:39.397

You can add breakpoint before exception is thrown. First go to Breakpoint Navigator (cmd + 6). In the bottom left corner mouse click plus button. OR You can use Instruments (/Developer/Applications/Instruments) to help detect usage of zombie objects. Reference

And When you add breakpoint review the picture will create by Xcode.

enter image description here

You can expand the stack trace using the slider at bottom use step over and over for line by line logs.

thanks hope this will help you

Xcode full stack trace

5 Answers5

Linked