What exactly happens when I perform a force quit?
What exactly happens when I perform a force quit?
- Subject: What exactly happens when I perform a force quit?
- From: Alexander Golec <email@hidden>
- Date: Wed, 12 Jan 2011 15:15:57 -0500
Hi all,
I've recently finished an intensive intro course to OS's, and I'm looking at my computer in a new light. I have a few questions I'd appreciate it if someone would take the time to answer.
First, what exactly happens when I perform a force quit on something? Secondly, how would I go about figuring this out on my own? I presume there is some sort of functionality for tracing the kernel, and I presume there is some way to log system calls made by an application, but I'm not sure either where to find it or which application to apply it to.
Would force quit be implemented on the level of the kernel, or in the realm of the standard library? Because on one hand, you can be brutal and just close all file handles and eject the program from the scheduler, while on the other hand anything above that level would require some arbitration on the part of the runtime environment.
Thanks,
Alex Golec _______________________________________________
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