Re: Who takes care of a crashing process?
Re: Who takes care of a crashing process?
- Subject: Re: Who takes care of a crashing process?
- From: Justin Walker <email@hidden>
- Date: Wed, 22 Sep 2004 10:28:56 -0700
On Sep 22, 2004, at 9:36, stephane sudre wrote:
On Sep 22, 2004, at 6:08 PM, Justin Walker wrote:
On Sep 22, 2004, at 8:13, Stephane Sudre wrote:
Stupid question probably:
When a process is properly exited, exit is called in the Kernel.
When a process crashes, exit is not called.
Is there a specific syscall called when a process crash?
Are you sure that exit() in the kernel is not called? If this were
not the case, we'd be leaking file entries, memory, and other
resources.
Well, I've patched the SYS_exit syscall and ran this program:
int main(...)
{
unsigned long * ohlala=NULL;
*ohlala=NULL;
}
I have not seen an exit call.
Ah. Once your program has crashed (e.g., with a memory fault/bus
error), code in its address space is no longer eligible for execution.
Despite that, however, the kernel's exit() procedure *is* called.
But maybe it's because there's no exit at the end of the code. The
previous answer is confusing me right now.
If this doesn't clarify things, ask.
Cheers,
Justin
--
Justin C. Walker, Curmudgeon-At-Large *
Institute for General Semantics | "Weaseling out of things is
what
| separates us from the animals.
| Well, except the weasel."
| - Homer J Simpson
*--------------------------------------*-------------------------------*
_______________________________________________
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