Re: Window-server access bug in parallel programming ... ?
Re: Window-server access bug in parallel programming ... ?
- Subject: Re: Window-server access bug in parallel programming ... ?
- From: Terry Lambert <email@hidden>
- Date: Sun, 04 Nov 2007 23:39:38 -0800
On Nov 4, 2007, at 9:47 PM, Eric Schlegel <email@hidden> wrote:
On Nov 4, 2007, at 6:12 PM, Jay Reynolds Freeman wrote:
What I see is a failure in thread zero of my app -- that's the one
where GUI I/O is done, always deep inside a display or
displayIfNeeded
of my main window. The actual crash is an EXC_BAD_ACCESS with
code KERN_PROTECTION_FAILURE in a function called szone_free, in
libSystem.B.dylib.
There have been many good suggestions in this thread which might
isolate your problem. But in mybexperience, when you hear hoofbeats,
it's best to look for horses.
Rather than add to the list of places where you should look, though,
why don't you just ask the code?
First, compile and link -g.
Second, before doing anything in the program, right at the top of main
(), use setrlimit() to set the core dump size to unlimited for cur.
Then when the program crashes, run gdb vs. The -g binary and the core
file, type bt, and it will list the calls leading up to the crash,
including the source code.
-- Terry
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden