Re: Apple crash reports
Re: Apple crash reports
- Subject: Re: Apple crash reports
- From: Michael Clark <email@hidden>
- Date: Tue, 30 Aug 2005 22:28:34 -0400
From what I know of this, you can do it, but it is tricky and not
well documented.
What you need to do is work with the Mach APIs to mess around with
the Mach exception handling machinery.
It appears that the crash reporter on OS X uses this facility to hook
into running apps, but you too can hook into this stuff, and
basically cut the crash reporter out of the loop and take over.
I believe Xcode is working in this space when you run your
applications through it. I had a heck of a time trying to do some
work with Mach exceptions a while ago, something seemed to interfere
with my stuff, and I assumed it was Xcode as I had to run my app
directly.
gdb definitely uses this stuff to implement some of it's debugging
facilities.
Anyhow, I am no expert with this stuff, but Tim Wood over at
OmniGroup is! :) He posted a great explanation of it back in 2000,
and you can read it here:
http://www.omnigroup.com/mailman/archive/macosx-dev/2000-June/
002030.html
Hope this helps.
Michael.
On 30-Aug-05, at 3:58 AM, Le Stang Jean-Baptiste wrote:
In fact it depends of the level of 'report' that is configured
using CrashReporterPrefs.app. I was using the 'Developer' setting,
if I switch to 'basic', I do not see the crash report either, but
I'm sure there is another to deactivate this like Xcode, but I
cannot find how this is done :(.
++ Jean-Baptiste
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40marketcircle.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden