On Mon, Apr 02, 2001 at 05:17:57PM -0400, Roland McGrath wrote:
> > Yes. Well, I now noticed that I could provoke it crashing badly when
> > I wait for proc to get E_BAD_ACCESS, and then run
> >
> > print mach_thread_self()
>
> Well, that is not surprising. You are telling gdb to call a function in
> the inferior process.
Ok. I am just happy that it seems to work in this simple trap w/o args,
because I didn't manage to access _hurd_thread_self in gdb and wouldn't know
how to get the thread port number any other way.
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
