From owner-freebsd-current Mon Jan 6 23:13: 1 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A0FB37B405; Mon, 6 Jan 2003 23:13:00 -0800 (PST) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4728143ED8; Mon, 6 Jan 2003 23:12:59 -0800 (PST) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.6/8.12.3) with ESMTP id h077Cs1e066400; Tue, 7 Jan 2003 00:12:54 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Tue, 07 Jan 2003 00:12:09 -0700 (MST) Message-Id: <20030107.001209.22369733.imp@bsdimp.com> To: rwatson@FreeBSD.ORG Cc: julian@elischer.org, jmallett@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: pthread ^T problem on recent -CURRENT: death in libc_r mutex From: "M. Warner Losh" In-Reply-To: References: X-Mailer: Mew version 2.1 on Emacs 21.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message: Robert Watson writes: : assuming it's something about poor signal handling in libc_r, actually. I've seen signal problems in devd after it forks a child. Before it forks a child ^C works, but after it does a system(3) to run a command, ^C no longer works. There's something really odd going on that I've not had time to figure it out. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message