This is not clearly an impossible conclusion. Bad RAM could cause
corruption in non-ECC machines which could cause a value offset or
reference pointer or address to be read incorrectly resulting in
exactly this same exception.
It's called a backtrace,
Actually the backtrace is but a part of the crash report.
This stuff is most useful to the programmers who wrote the
application, but hardly at all to others (which is a large set that
includes most system administrators.)
Hardly. A good sysadmin should be able to map and follow a crash dump
and identify the faulty code. At one point this was a manditory skill
(how else would you debug the kernel and wares you're running for
your organization), but with many sysadmins also getting coffee and
donuts for the office staff as part of their jobs these days it's
just one more thing that seems to be lost on many holding this job
title.
If it keeps happening, then you've got a problem with servermgrd to
investigate.
In any case it should be reported to Apple, using the mechanism that
generated the report on the console.
Actual bad RAM problems rarely crash things in such a friendly and
helpful fashion that the operating system has an opportunity to
output this handy report.
Umm... Even a kernel panic generates such a report.
--
-dhan
------------------------------------------------------------------------
Dan Shoop AIM: iWiring
Systems & Networks Architect http://www.ustsvs.com/
email@hidden http://www.iwiring.net/
1-714-363-1174
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/macos-x-server/email@hidden
