DiscussWorldIssues - Socio-Economic Religion and Political Uncensored Debate - View Single Post

**yasalaioqe** · 11-25-2007, 01:23 AM

Turned out to be Kernel panics caused by one of my application not having been updated to match the new Leopard. Kernel panics are caused by faulty apps or hardware, so I'm afraid this "historical" event was a dud.

I totally agree with ejstans: a faulty app should not be able to cause a kernel panic, no matter how badly coded. To cause a kernel panic the code need to be run in kernel space, which hopefully most apps are not. A bad driver or faulty hardware is probably the safest bet.

11-25-2007, 01:23 AM	#15
yasalaioqe Join Date Oct 2005 Posts 450 Senior Member	Turned out to be Kernel panics caused by one of my application not having been updated to match the new Leopard. Kernel panics are caused by faulty apps or hardware, so I'm afraid this "historical" event was a dud. I totally agree with ejstans: a faulty app should not be able to cause a kernel panic, no matter how badly coded. To cause a kernel panic the code need to be run in kernel space, which hopefully most apps are not. A bad driver or faulty hardware is probably the safest bet.
	Quote