Date: Thu, 30 Aug 2001 03:07:22 +0900 From: Fuyuhiko Maruyama <fuyuhik8@is.titech.ac.jp> To: Daniel Eischen <eischen@vigrid.com> Cc: hackers@FreeBSD.ORG Subject: Re: libc_r, signals and modifying sigcontext Message-ID: <55itf6ivtx.wl@tripper.private> In-Reply-To: <55k7zmiwop.wl@tripper.private> References: <20010729011656.A11337@sharmas.dhs.org> <Pine.SUN.3.91.1010729093922.16774A-100000@pcnet1.pcnet.com> <20010729170402.A18538@sharmas.dhs.org> <55k7zmiwop.wl@tripper.private>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <fuyuhik8@is.titech.ac.jp> Matsuoka laboratory, Department of Mathematical and Computing Sciences, Graduate School of Information Science and Engineering, Tokyo Institute of Technology. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55itf6ivtx.wl>