First of all I appologise for the horrible late reply, but better late then never, eh?
It looks like an interrupt routine is causing the SEGV? (eip is 0x1, wouldn't this be in the x86 interrupt vector?, would that explain why the backtrace cant give specific info?) Well, the info in frames 0 and 1 is kinda useless, the problem happens before frame 9, somewhere. It looks like something passes a NULL pointer to thread_continue(), and things just go bogus from there. Could you try and see what happens before those frames (like what tries to send thread_continue() a NULL, and why it is NULL)? And "backtrace full" is more usefull then a plain "backtrace". _______________________________________________ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd
