Re: single machine debugging?/advice for noob on OS X panic analysis
Re: single machine debugging?/advice for noob on OS X panic analysis
- Subject: Re: single machine debugging?/advice for noob on OS X panic analysis
- From: Markus Hitter <email@hidden>
- Date: Wed, 3 Nov 2004 09:10:52 +0100
Am 02.11.2004 um 19:07 schrieb Eric R Johnson:
Anyone with a dual cpu mac and an extended time to let the app run
(while downloading and seeding torrents) will probably see a panic,
though.
This should be already enough for a bug report. Apple engineers have
few time but many Macs so they just have to set up one and wait (while
working on other things ;-) ) for the panic to occur.
Then, they have sources for the java engine so they can get a more
meaningful backtrace. Hopefully, they agree they have to fix something
in their engine.
Third, you make sure they are aware of the problem.
I'll see if I can push to get users to submit information to get a
rough idea of MTBF or TDR trends. It's pretty hard to get good data
out of your average user, though.
Azureus always works fine here. Great work. But then, I have single-CPU
Macs, only. :-)
Markus
- - - - - - - - - - - - - - - - - - -
Dipl. Ing. Markus Hitter
http://www.jump-ing.de/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden