Thanks for your reply.
On Sat, Oct 24, 2009 at 6:03 PM, Jens Alfke <j...@mooseyard.com> wrote:
>
> It would be really good to get a backtrace. Are you launching the process
> with gdb, or at least attaching before the crash?
Yes. I'm launching with gdb and pass the "debug" argument to Screen
Saver Engine. This way the screen saver is running on the desktop
window level.
> And after the crash, gdb
> is confused and can't get info about the process?
Sort of. I think the problem is no app can have keyboard focus as long
as the screensaver is running/frontmost. So Xcode is not responding to
keyboard events until I terminate the process.
> If you run without gdb, do you get a regular "unexpectedly quit" alert with
> the option to send a crash report (which includes a backtrace)?
No. The process just hangs and I have to force a reboot.
> Have you tried running with malloc in scribbling/heap-checking mode, to see
> if anything funky's going on with the heap? ('man malloc' for details on the
> environment variables to set for this.)
I'm not sure what to expect, but I did try just now to enable most of
these settings and they didn't return anything that looked helpful in
gdb.
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
