> On Oct 15, 2015, at 11:27, Jens Alfke <j...@mooseyard.com> wrote: > > >> On Oct 15, 2015, at 3:16 AM, Alex Hall <mehg...@icloud.com >> <mailto:mehg...@icloud.com>> 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. > > 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 -- Have a great day, Alex Hall mehg...@icloud.com
_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (Xcode-users@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to arch...@mail-archive.com
