I missed one thing to say,
When I try to know what's happen in the libc_r, I use libc_r with
DEBUG_SIGNAL defined. There seems to be something wrong with libc_r's
signal handler when it cannot find the thread to handle signal, libc_r
seems to refer some phantom thread that doesn't exist and it may cause
another fault. If you also use libc_r with DEBUG_SIGNAL defined, you
can see the problem during execution of my previous sample program
(test.c).
Thanks.
--
Fuyuhiko MARUYAMA <[EMAIL PROTECTED]>
Matsuoka laboratory,
Department of Mathematical and Computing Sciences,
Graduate School of Information Science and Engineering,
Tokyo Institute of Technology.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
