From owner-freebsd-threads@FreeBSD.ORG Wed Sep 8 16:17:08 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1524E16A4CE for ; Wed, 8 Sep 2004 16:17:08 +0000 (GMT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id B528E43D49 for ; Wed, 8 Sep 2004 16:17:07 +0000 (GMT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.10/8.12.10) with ESMTP id i88GH5Jt020668 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 Sep 2004 12:17:05 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id i88GGwB4056707; Wed, 8 Sep 2004 12:16:58 -0400 (EDT) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16703.12410.319869.29996@grasshopper.cs.duke.edu> Date: Wed, 8 Sep 2004 12:16:58 -0400 (EDT) To: freebsd-threads@freebsd.org In-Reply-To: <16703.11479.679335.588170@grasshopper.cs.duke.edu> References: <16703.11479.679335.588170@grasshopper.cs.duke.edu> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Subject: Re: Unkillable KSE threaded proc X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Sep 2004 16:17:08 -0000 Andrew Gallatin writes: > > If I send a kill -9 to a threaded process in a creative way, I see it > get stuck forever exiting. (run from a /bin/sh script, > killed via ssh $MACHINE skill -9 -u gallatin) > > It shows up in a ddb ps like this: > > 3403 c1652540 e52fe000 1387 1 3401 000c402 (threaded) mx_pingpong > thread 0xc2de4c60 ksegrp 0xc15b2200 [SUSP] > FWIW, before sending it an skill -9, another run of the same program will show up in ddb ps like this: 3514 c1b65540 e6842000 0 3058 3514 000c002 (threaded) mx_pingpong thread 0xc2e0ab00 ksegrp 0xc1b60100 [SLPQ kserel 0xc1b6015c][SLP] thread 0xc1af7840 ksegrp 0xc1b60100 [CPU 1][kse 0xc1af8c00] thread 0xc2de5840 ksegrp 0xc1b60100 [SLPQ mx cv 0xc16b9e40][SLP] thread 0xc2de56e0 ksegrp 0xc2de3800 [SLPQ ksesigwait 0xc1b65640][SLP] Since there's only one thread left in the hung case, could it just be some sort of race in the exit code? Thanks, Drew