There is currently a problem with debugging using Xcode. All stack traces show only the last two calls made. Cannot use lldb console. For example, a simple unrecognized selector error shows only this trace log
lldb
unrecognized selector
* thread #1: tid = 0x2503, 0x32d2e960 libobjc.A.dylib`objc_exception_throw, stop reason = breakpoint 1.1 frame #0: 0x32d2e960 libobjc.A.dylib`objc_exception_throw frame #1: 0x37c4ae06 CoreFoundation`-[NSObject(NSObject) doesNotRecognizeSelector:] + 170
Try printing [NSThread callStackSymbols] from the debugger, which sometimes works when the debugger does not. It doesnβt surprise me that
[NSThread callStackSymbols]
In addition, my experience is that GDB is much more reliable.
A simple restart of Xcode solved the problem. But this error continues to occur some time later. I will report an error.
Rewinding through Objective-C runtime functions can be complicated on hand, the assembly is manually configured, and lldb may have difficulty deciding how to unwind them. In this case, it seems that he got one frame further, and then could not go further.