That is a resource-shortage crash. If you got a stack trace of the crash
(e.g. use ddb if that still works), then we could see what kind of kernel
object it was allocating. It might be a general eat-all-memory bug, or it
might be a fast leak in some particular kind of kernel object (ports, etc).
Package: gnumach
Version: CVS Snapshots
When doing large builds, I have gotten a lot of kernel panics (gnumach).
They are (so far) caused without exception when ranlib is running. Just
now, I got a chance to see the console before it rebooted itself (and
as usual, trashed the partition). It sai
