Getting poor stack traces
Getting poor stack traces
- Subject: Getting poor stack traces
- From: Rick Mann <email@hidden>
- Date: Tue, 30 Jul 2013 13:30:45 -0700
I'm trying to debug a problem where I'm inserting nil into a placeholder array. I break on exceptions, and it stops dutifully, but the stack is useless. So I set a symbolic breakpoint on -[__NSPlaceholderArray initWithObjects:count:]. It stops just fine, but again, the stack seems truncated:
(lldb) bt
* thread #1: tid = 0x2403, 0x32ffe2a8 CoreFoundation`-[__NSPlaceholderArray initWithObjects:count:], stop reason = breakpoint 3.1
frame #0: 0x32ffe2a8 CoreFoundation`-[__NSPlaceholderArray initWithObjects:count:]
frame #1: 0x32ffe1bc CoreFoundation`+[NSArray array] + 40
frame #2: 0x34ecd2be UIKit`+[UIWindow allWindowsIncludingInternalWindows:onlyVisibleWindows:] + 66
In this case, the call is fine and will execute normally, so there's no stack corruption going on (yet). I don't think there was any even after the exception I'm encountering.
Is there anything I can do?
--
Rick
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden