On 7/11/07 4:13 PM, "Paul Berkowitz" <[EMAIL PROTECTED]> wrote:
> That's nonsense. In OS X, applications don't cause system crashes as they
> could in OS 6-9. They might themselves crash, but they don't bring down the
> system. OS X is multithreaded.
In OS X, each app runs in its own isolated memory space. So in the vast
majority of cases, when an app crashes, the OS and other running apps are
not affected. But it's possible for an app to request a service from the
OS, using badly formed or unexpected parameters, causing the OS to crash.
In theory, the OS designers prevent such events by installing validation
tests to detect bad input. But OS programmers are human, and their
validation tests and error recovery routines can be imperfect. And of
course, a bug in the OS can cause it to crash, even when the service
requests are valid.
I don't know what caused the kernel panic that I saw yesterday. Here's the
log entry. Not much to go on. Maybe someone on the list can identify a
clue. This was on a Power Mac Dual 1.25 GHz, running OS X 10.4.10 and
Entourage 11.3.3.
Tue Jul 10 18:30:12 2007
panic(cpu 0 caller 0x000A4CC8): simple lock (0x0038DFA0) deadlock detection,
pc=0x0003C1B8
Latest stack backtrace for cpu 0:
Backtrace:
0x000952D8 0x000957F0 0x00026898 0x000A4CC8 0x0003C1B8 0x0002E8D4
0x000ABCAC 0x00000000
Proceeding back via exception chain:
Exception state (sv=0x3F600500)
PC=0x90033D08; MSR=0x0200F030; DAR=0xE174A000; DSISR=0x42000000;
LR=0x907EC8BC; R1=0xBFFFCE30; XCP=0x00000030 (0xC00 - System call)
Kernel version:
Darwin Kernel Version 8.10.0: Wed May 23 16:50:59 PDT 2007;
root:xnu-792.21.3~1/RELEASE_PPC
--
Julian Vrieslander <[EMAIL PROTECTED]>
--
To unsubscribe:
<mailto:[EMAIL PROTECTED]>
archives:
<http://www.mail-archive.com/entourage-talk%40lists.letterrip.com/>
old-archive:
<http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
