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). _______________________________________________ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd
- Bug#82600: ranlib causes kernel panics Neal H Walfield
- Roland McGrath