Re: advanced debugging?

> On Oct 15, 2015, at 01:38, Roland King wrote: > > >> On 15 Oct 2015, at 11:38, Alex Hall wrote: >> >> For these stack traces, is there any way for it to point right at the >> offending line in context? That is, instead of a generic array.append call, >>

Re: advanced debugging?

> On Oct 15, 2015, at 3:16 AM, Alex Hall 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

Re: advanced debugging?

> On Oct 15, 2015, at 20:06, Jens Alfke wrote: > > >> On Oct 15, 2015, at 5:03 PM, Alex Hall > > wrote: >> >> I'm sorry to be asking such basic questions, but what do you mean by the >> debug console? The place where errors

Re: advanced debugging?

> On Oct 15, 2015, at 5:03 PM, Alex Hall wrote: > > 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 Yes, it does. When the app is paused, an “(lldb)”

Re: advanced debugging?

On Oct 15, 2015, at 7:33 PM, Alex Hall wrote: > > >> On Oct 15, 2015, at 20:06, Jens Alfke > > wrote: >> >> >>> On Oct 15, 2015, at 5:03 PM, Alex Hall >> > wrote: >>> >>> I'm

Re: advanced debugging?

> On Oct 15, 2015, at 11:27, Jens Alfke wrote: > > >> On Oct 15, 2015, at 3:16 AM, Alex Hall > > wrote: >> >> I don't know how much sense this will make, since VO groups things together, >> probably differently from what

Re: advanced debugging?

> On Oct 15, 2015, at 20:52, Ken Thomases wrote: > > On Oct 15, 2015, at 7:33 PM, Alex Hall > wrote: >> >> >>> On Oct 15, 2015, at 20:06, Jens Alfke >> > wrote: >>> >>>

Re: advanced debugging?

> On Oct 14, 2015, at 5:59 AM, Alex Hall wrote: > > Cinnamon(1775,0x10086b000) malloc: *** mach_vm_map(size=72018011619328) > failed (error code=3) > *** error: can't allocate region > *** set a breakpoint in malloc_error_break to debug FYI, the error here is that

Re: advanced debugging?

To add a breakpoint on malloc_error_break do command 7 which shows the break points in the navigator view. At the bottom of the view is a plus button. Click the button. Then select Add Symbolic Breakpoint... From the menu. Enter malloc_error_break in the symbol text field and hit return. Done.

Re: advanced debugging?

> On Oct 14, 2015, at 22:32, Jens Alfke wrote: > > >> On Oct 14, 2015, at 7:08 PM, Alex Hall wrote: >> >> Unfortunately this didn't reveal much of anything that I can tell. It goes >> straight from >> 5 Array.append(A) -> (), >> to >> 0

advanced debugging?

Hello list, I have a Mac app which was going well until I tried to add a web view. It was giving me a lot of trouble, so I've left it out for the moment. However, after I tried to remove it, my app stopped working. My debug console shows this error, which happens after the main view

Re: advanced debugging?

Thanks, everyone. Now I know how to use symbolic breakpoints and when to do so, and that the stack trace appears in the debug table. I even discovered that the editor shows the specifics of whatever item in the trace you focus on, not that I have the first clue what all that means. :)

Re: advanced debugging?

> On Oct 14, 2015, at 7:08 PM, Alex Hall wrote: > > Unfortunately this didn't reveal much of anything that I can tell. It goes > straight from > 5 Array.append(A) -> (), > to > 0 swift_slowAlloc, > and that's it. Well, there's more before that, but nothing after. I

Re: advanced debugging?

I expect that bug was there, before you added the web view, but something about removing the web view led a previously-latent bug to become active. Try bisecting your code, that is, remove half your source, try to reproduce the bug, then put that first half back in and remove the other half. Now

Re: advanced debugging?

> On 15 Oct 2015, at 11:38, Alex Hall wrote: > > For these stack traces, is there any way for it to point right at the > offending line in context? That is, instead of a generic array.append call, > could it say line 119 in MyModel.swift, or wherever the problem is? It