Date: Tue, 07 Jan 2003 00:12:09 -0700 (MST) From: "M. Warner Losh" <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 Message-ID: <20030107.001209.22369733.imp@bsdimp.com> In-Reply-To: <Pine.NEB.3.96L.1030105153315.90032A-100000@fledge.watson.org> References: <Pine.BSF.4.21.0301051220200.91683-100000@InterJet.elischer.org> <Pine.NEB.3.96L.1030105153315.90032A-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <Pine.NEB.3.96L.1030105153315.90032A-100000@fledge.watson.org>
Robert Watson <rwatson@FreeBSD.ORG> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030107.001209.22369733.imp>