Mac Crash Reports

[Sub Judicator]

Hi all.

So, I am a mac user, and play with a bunch of PC users. We are basically stuck on 2.2.1 since that is the last build that works with my MacBook Pro, OS 10.4. I know I should have posted about this before, but frankly, I am embarrassed!

Where the heck does warzone or my mac store its crash reports? When I search for crash reports, I get warzone.crash.log in my library of logs (Users/(my name)/Library/Logs/CrashReporter), but it says that the last time warzone.crash.log has been updated was 11/07.

My "ended processes crash log" reports the last crash at 11/02/09

Every single version for mac since 2.2.1 freezes early and often after starting a skirmish game or multiplayer... the latest, 2.3 beta 4 froze today after about 10 minutes of play, forcing me to force-quit it. But for the life of me I have no clue where any of the records for these crashes or freezes or force quits are going... any clues? I've googled around a bit, but those answers lead me to the crash log for warzone that apparently hasn't recorded anything since November!

I believe one of the developers has basically said "most Mac crashes have to do with the video card driver," but I'd love to know for sure. Would love any advice from anyone on where to look!

-SJ

[Zarel]

Freezing sometimes doesn't generate crash logs. When Warzone freezes, the best you can get is a stack trace.

While Warzone is frozen, before you force quit it:

Open Terminal.app

Enter:

Code: Select all

gdb
attach Warzone
backtrace

And copy/paste the results over here.

Also: Have you tried playing with music disabled? How about all sound?

[Buginator]

Hi all.
I believe one of the developers has basically said "most Mac crashes have to do with the video card driver," but I'd love to know for sure. Would love any advice from anyone on where to look!

-SJ

Actually, a crash isn't a lockup.

In this case, I think the issue is the older buggy libs we are using, but hopefully, the 2.3RC1 will update all the libs.