On Wed, Mar 28, 2001 at 04:28:28PM -0500, Roland McGrath wrote:
> > 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!
Wonderful.
> I suspect that is some kernel bug having to do with wired threads.
> Can you get the kernel backtrace?
I wouldn't know how to get it, so I don't know if I can. What do I need for
this?
> You might try commenting out the code in
> proc that wires things for the proc you run in the sub-hurd.
Which would be?
2000-03-13 Roland McGrath <[EMAIL PROTECTED]>
Don't call cthread_wire; it's a no-op in GNU anyway.
If it isn't "wire" I am looking for, I don't know what I am looking for (a
grep showed nothing in proc/).
> > 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.
I think I know how to do this, so I will try this first.
Sometimes I wonder if the kernel ring buffer proposed by RMS wouldn't be
helpful in situations like this.
Thanks,
Marcus
--
`Rhubarb is no Egyptian god.' Debian http://www.debian.org [EMAIL PROTECTED]
Marcus Brinkmann GNU http://www.gnu.org [EMAIL PROTECTED]
[EMAIL PROTECTED]
http://www.marcus-brinkmann.de
_______________________________________________
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-hurd
