Re: mach in signal handler
Re: mach in signal handler
- Subject: Re: mach in signal handler
- From: Steve Checkoway <email@hidden>
- Date: Fri, 26 Jan 2007 11:25:11 -0800
On Jan 26, 2007, at 6:29 AM, Dave Zarzycki wrote:
On Jan 25, 2007, at 7:25 PM, Steve Checkoway wrote:
If it matters, I would only be calling it from within the signal
handler which I don't allow to be reentrant. (If another signal
happens while I'm in the handler, I give up and just die.)
Well, one of our library calls might be in the middle of a Mach
based API. :-(
I was afraid that might be the case. If that were the case, what
would actually happen? Would the later invocation stomp on the
suspended one (which would be fine because the app will be killed
before the signal handler exits) or is there some shared state that
would be in an inconsistent state or would it block waiting for the
other code to leave the handler?
I am already suspending all other threads using mach apis and that
seems to work. At least, I have yet to have a problem with it.
I have zero preferences on which api to use to get the job done,
so if you can suggest a more suitable one, I'd be more than happy
to use it.
Why write code at all then? What's wrong with Apple's CrashReporter
facility? :-)
Two things. One, it hasn't been triggered by that point and two,
there're no programatic hooks I know of.
--
Steve Checkoway
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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