> > Do you get "Crashing system; essential task exec died"?
>
> I have gotten that. This time, however, I did not get a chance to look
> at the console before init crashed the system.
Perhaps you should hack init to do a device_read from the console
before it reboots, so you can see all the msgs.
> I have seen both proc and exec crash during long compiles. Next time, I
> will attach gdb to both and hopefully get a backtrace. Additionally,
> must I be running in a subhurd for this to work?
If you can run a sub-hurd, then do. It is by far the easiest way to debug
these problems. In the case of exec, you should not really have any
problem with debugging on the failing hurd itself. But for proc it is
likely to be a real pain in the ass. And either way, life is much easier
if you can use your top hurd for poking around, running vmstat, and all the
rest, without asking your sub-hurd to do anything at all while you are
trying to examine its state.
_______________________________________________
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-hurd
