Date: Wed, 27 Oct 2004 12:20:21 GMT From: David Xu <davidxu@freebsd.org> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/72979: unkillable process(es) stuck in `STOP' state Message-ID: <200410271220.i9RCKLeu045569@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/72979; it has been noted by GNATS. From: David Xu <davidxu@freebsd.org> To: Mikhail Teterin <mi+kde@aldan.algebra.com> Cc: Ken Smith <kensmith@cse.buffalo.edu>, Mikhail Teterin <mi+mx@aldan.algebra.com>, Michael Nottebrock <michaelnottebrock@gmx.net>, 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 <pid of gdb> >= >= 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200410271220.i9RCKLeu045569>