On Oct 15, 2015, at 8:03 PM, Alex Hall wrote:
On Oct 15, 2015, at 3:16 AM, Alex Hall < email@hidden> wrote:
I don't know how much sense this will make, since VO groups things together, probably differently from what you see visually, but I'll give it a shot.
In the debugger console, enter the command “bt”. This will dump a backtrace of the stack. Then copy that text and paste it into a reply, and we can look at it.
I'm sorry to be asking such basic questions, but what do you mean by the debug console? The place where errors and print/log statements appear doesn't take input, and that's the only place I know of labeled as being a debug anything. There's the debug bar group, but there are no edit fields in there.
Actually it does.
For the sighted amongst us, in the debug console that appears on the bottom of the screen. The left side of it can show your variables and the right side can output log statements and you can also enter great commands like po for print object.
If you have an object that is an NSString, and you have hit a breakpoint, you can type into the right pane po and the name of your string object and it will be displayed in the log in that window.
Oh, also: if you haven’t already, enable the Address Sanitizer (it’s a checkbox in the Diagnostics tab of the Run section of the scheme editor.) If the crash is due to earlier heap corruption, this might catch that.
—Jens
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
|