Re: Reboots?

[Roland McGrath]

> Yeah, did that. it entered gdb all right, and gdb switched to the crashing
> thread (10 of 19). When I left gdb it crashed with "panic: thread_invoke",

Exciting!  I suspect that is some kernel bug having to do with wired threads.
Can you get the kernel backtrace?  You might try commenting out the code in
proc that wires things for the proc you run in the sub-hurd.

We might want to add flags to init and proc (and whatever else there is)
to not do wiring, since you often might want to avoid it when debugging
a sub-hurd.

> and so I lost my log, but it went like this:

That looks like there was a bad jump, or a stack clobberation that resulted
in one (i.e. clobbering saved pc/fp on the stack and then returning).

You might do some hack in the demuxer or something that sets a global
variable indicating the last RPC that was being handled.  Then you might
get an idea what code is running just before the crash.