From owner-freebsd-hackers Wed Aug 29 11: 5: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from matsulab.is.titech.ac.jp (matsulab.is.titech.ac.jp [131.112.35.129]) by hub.freebsd.org (Postfix) with ESMTP id A3FD837B408 for ; Wed, 29 Aug 2001 11:04:57 -0700 (PDT) (envelope-from fuyuhik8@is.titech.ac.jp) Received: from tripper.private by matsulab.is.titech.ac.jp (8.8.8+Sun/3.7W) id DAA05138; Thu, 30 Aug 2001 03:04:53 +0900 (JST) Date: Thu, 30 Aug 2001 03:07:22 +0900 Message-ID: <55itf6ivtx.wl@tripper.private> From: Fuyuhiko Maruyama To: Daniel Eischen Cc: hackers@FreeBSD.ORG Subject: Re: libc_r, signals and modifying sigcontext In-Reply-To: <55k7zmiwop.wl@tripper.private> References: <20010729011656.A11337@sharmas.dhs.org> <20010729170402.A18538@sharmas.dhs.org> <55k7zmiwop.wl@tripper.private> User-Agent: Wanderlust/2.6.0 (Twist And Shout) on XEmacs/21.5.1 (anise) MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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 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