Just-in-time debugging / CrashReporterPrefs
Just-in-time debugging / CrashReporterPrefs
- Subject: Just-in-time debugging / CrashReporterPrefs
- From: "Gammah Radiation" <email@hidden>
- Date: Tue, 2 Oct 2007 11:02:36 -0500
Hi all-
I have suddenly gotten into a state where my preferences for
post-mortem debugging are no longer working.
I was debugging a crash in an application that at one point caused the
machine to become unresponsive. I powered the machine off, and when
the machine came back up, my CrashReporterPrefs preference for
'developer' were no longer honored.
I tried removing the ~/Library.../com.apple.CrashReporterPrefs.plist
file (which already contained the 'developer' value), then rebooting
and resetting the preference to developer. I also made sure that
crashreporterd was still being started at boot, which it is. When an
application crashes, I still get crashlogs being put in /Library and
~/Library, but I need to be able to get gdb involved at the point of
the crash. The application I'm debugging behaves differently when
started with the debugger before the crash versus having
crashreporter start the debugger at the moment of the crash.
Booting into another OSX partition, installing the dev tools, and
setting the preference to 'developer' allows me to debug a crash on
that OSX install; but obviously I need to be able to recover this
ability in the partition I use day-to-day.
Can anyone shed light on this? Has anyone seen this happen? I
considered removing and reinstalling /Developer, but I figured since
crashdump and crashreporterd are in /usr/libexec, that this would
likely be a waste of time.
Thanks for any assistance or thoughts, even if you aren't 100% sure.
Anything to get me thinking would help.
-t.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden