Panther Poisoning......bad beef?
hey, I've been off of AI for a few days, this thread title is stupid, sorry about that!
I finally gave in and installed Panther on my 600Mhz 12" iBook w/ 384Mb RAM. It's not bad, speedwise, but within the first 30 minutes I discovered that Safari wouldn't stay opened thirty seconds before crashing. Same thing with Mozilla. Software Update would hiccup and crash too. MS Word did it some today too.
Not wanting this to be a Genius Bar post I have to put the question out there like this to those who might know if this is a widespread issue or if (more likely) this is indicative of an installation that just didn't "take".
Here's a bit of the code that Panther's crash report app shows me:
Date/Time: 2004-03-05 01:50:19 -0500
OS Version: 10.3.2 (Build 7D24)
Report Version: 2
Command: Safari
Path: /Applications/Safari.app/Contents/MacOS/Safari
Version: 1.2 (125)
PID: 1625
Thread: 0
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at 0xbbadbeef
So is it like the crash report says (note that last bit)? Have I gotten 'hold of some Badbeef? Should I reinstall from the ground up? Running on IE is just not good!!
I finally gave in and installed Panther on my 600Mhz 12" iBook w/ 384Mb RAM. It's not bad, speedwise, but within the first 30 minutes I discovered that Safari wouldn't stay opened thirty seconds before crashing. Same thing with Mozilla. Software Update would hiccup and crash too. MS Word did it some today too.
Not wanting this to be a Genius Bar post I have to put the question out there like this to those who might know if this is a widespread issue or if (more likely) this is indicative of an installation that just didn't "take".
Here's a bit of the code that Panther's crash report app shows me:
Date/Time: 2004-03-05 01:50:19 -0500
OS Version: 10.3.2 (Build 7D24)
Report Version: 2
Command: Safari
Path: /Applications/Safari.app/Contents/MacOS/Safari
Version: 1.2 (125)
PID: 1625
Thread: 0
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at 0xbbadbeef
So is it like the crash report says (note that last bit)? Have I gotten 'hold of some Badbeef? Should I reinstall from the ground up? Running on IE is just not good!!
Comments
http://www.opensource.apple.com/darw...WQAssertions.h
Where one finds:
// CRASH -- gets us into the debugger or the crash reporter -- signals are ignored by the crash reporter so we must do better
#define CRASH() *(int *)0xbbadbeef = 0
Your WebCore installation is bad. \
If that fails, yeah, you could try an "Archive and Install" reinstallation.
D