On Thu, Mar 13, 2003 at 08:10:25PM +0100, Robert Millan wrote: > I was running an highly resource consumption process when Mach > paniced. The reason is probably related to bug #82600 > > But the problem i'm reporting is that Mach unexpectedly rebooted the > machine after panicing. The error message i could read was something > similar to: > > panic: kalloc: memory exhausted in zalloc > > (it's not exact, as i didn't have time to write it down. there was a > number i ommited and maybe the "zalloc/kalloc" order was reversed) > > Mach should realy stop after a panic and let the user read the > message, instead of rebooting.
I was just reading the FAQ on http://www.gnu.org/software/hurd/faq.en.html and noticed this: --8<-- 5.5. When GNU/Hurd crashes, GNU Mach automatically reboots. Is there anyway I can make it pause so I can write down the error? {MB} Pass the `-H' option to init (add it to the boot command line), and `init' will tell Mach to enter the kernel debugger instead to rebooting it. At the debugger prompt (`db>'), you can type `reboot' any time to reboot the system. --8<-- Maybe that helps in your case? Michael _______________________________________________ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd
