kern/72979: unkillable process(es) stuck in `STOP' state
davidxu at freebsd.org
Wed Oct 27 05:20:21 PDT 2004
The following reply was made to PR kern/72979; it has been noted by GNATS.
From: David Xu <davidxu at freebsd.org>
To: Mikhail Teterin <mi+kde at aldan.algebra.com>
Cc: Ken Smith <kensmith at cse.buffalo.edu>,
Mikhail Teterin <mi+mx at aldan.algebra.com>,
Michael Nottebrock <michaelnottebrock at gmx.net>, re at freebsd.org,
davidxu at t2t2.com, davidxu at viatech.com.cn,
freebsd-gnats-submit at 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!
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.
More information about the freebsd-bugs