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. :)
Unfortunately this didn't reveal much of anything that I can tell. It goes straight from 5 Array.append<A>(A) -> (), to 0 swift_slowAlloc, and that's it. Well, there's more before that, but nothing after. I guess I was hoping for a line number in a specific file, but maybe there's no way to get that specific? Or am I looking at the wrong stack trace? > On Oct 14, 2015, at 12:00, Jens Alfke <j...@mooseyard.com> wrote: > > >> On Oct 14, 2015, at 5:59 AM, Alex Hall <mehg...@icloud.com >> <mailto:mehg...@icloud.com>> 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 something called malloc with a size of > 0x418000000000, which is obviously bogus. Hopefully the reason will be clear > once you can examine the backtrace. Most likely something computed the size > based on a value in a garbage (uninitialized or overwritten) variable. > > —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
