Re: How to intercept exceptions in Carbon
Re: How to intercept exceptions in Carbon
- Subject: Re: How to intercept exceptions in Carbon
- From: Wincent Colaiuta <email@hidden>
- Date: Mon, 13 Aug 2007 17:44:44 +0200
El 13/8/2007, a las 13:18, Steve Checkoway escribió:
On Aug 13, 2007, at 3:19 AM, Wincent Colaiuta wrote:
One of the principal obstacles to doing this is that the crash
reporter daemon already takes your per-application exception
handling port and as far as I know there's no way to wrest control
away from it; you therefore have to rely on per-thread exception
ports.
Are you sure about this? I was told to consider using mach for this
when I asked on the darwin-dev list (which is probably a better
place for this thread than xcode-users).
The last time I looked at this (within the last year) that's what
Apple DTS told me.
Furthermore, using signals, I have been able to catch and generate
backtraces (for powerpc at least, I have no i386 so I haven't
written that code yet) for almost every crash.
That didn't work for me... I found that the crash reporter still
launched even though I was catching the signals and the program
continued executing.
Are you sure that the crash reporter will log it even if it's
disabled?
No, not sure but I believe it to be the case.
It seems better to catch it, fork a new process, write(2) some data
to the new process and have that handle it.
If you use the Apple-generated crash reports then you get a bunch of
other stuff for free, like address-to-symbol conversion, binary image
lists, process info and the like.
Cheers,
Wincent
_______________________________________________
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