From owner-freebsd-bugs@FreeBSD.ORG Wed Oct 27 12:20:21 2004 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A8A2B16A4CE for ; Wed, 27 Oct 2004 12:20:21 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 984B243D45 for ; Wed, 27 Oct 2004 12:20:21 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id i9RCKLxx045570 for ; Wed, 27 Oct 2004 12:20:21 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i9RCKLeu045569; Wed, 27 Oct 2004 12:20:21 GMT (envelope-from gnats) Date: Wed, 27 Oct 2004 12:20:21 GMT Message-Id: <200410271220.i9RCKLeu045569@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: David Xu Subject: Re: kern/72979: unkillable process(es) stuck in `STOP' state X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: David Xu List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2004 12:20:21 -0000 The following reply was made to PR kern/72979; it has been noted by GNATS. From: David Xu To: Mikhail Teterin Cc: Ken Smith , Mikhail Teterin , Michael Nottebrock , re@freebsd.org, davidxu@t2t2.com, davidxu@viatech.com.cn, freebsd-gnats-submit@freebsd.org Subject: Re: kern/72979: unkillable process(es) stuck in `STOP' state Date: Wed, 27 Oct 2004 20:13:11 +0800 Mikhail Teterin wrote: >On Tuesday 26 October 2004 10:53 pm, Ken Smith wrote: > >= % gdb prog # can be anything >= gdb> break main >= gdb> run >= gdb> ^Z >= % ps >= % kill >= >= Process for prog will be left behind and can't be killed. With David's >= patch process for prog dies along with gdb. > >Should not just the gdb be killed in the above scenario -- without the >explicit killing of prog? > >Or does killing the tracer always imply killing the tracee? Thanks! > > -mi > > > > > Killing tracer should always kill tracee as well, this becauses tracer may have changed tracees 's code or data, and if tracer dies, the tracee will be segment fault otherwise if we let it continue. David Xu