From owner-freebsd-hackers  Sun Feb 23 02:36:53 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id CAA03191
          for hackers-outgoing; Sun, 23 Feb 1997 02:36:53 -0800 (PST)
Received: from paris.CS.Berkeley.EDU (paris.CS.Berkeley.EDU [128.32.34.47])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA03186
          for <freebsd-hackers@freebsd.org>; Sun, 23 Feb 1997 02:36:51 -0800 (PST)
Received: from paris.CS.Berkeley.EDU (localhost.Berkeley.EDU [127.0.0.1]) by paris.CS.Berkeley.EDU (8.8.3/8.8.2) with ESMTP id CAA16290 for <freebsd-hackers@freebsd.org>; Sun, 23 Feb 1997 02:36:50 -0800 (PST)
From: Josh MacDonald <jmacd@CS.Berkeley.EDU>
Message-Id: <199702231036.CAA16290@paris.CS.Berkeley.EDU>
To: freebsd-hackers@freebsd.org
Subject: killing traced processes
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <16283.856694207.1@paris.CS.Berkeley.EDU>
Date: Sun, 23 Feb 1997 02:36:48 -0800
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I sometimes run into the following:

* Running process in gdb.
* Interupt, process ends up stopped, I don't really know how tracing
  works, so I don't know exactly what happens.  ps shows state="TX",
  meaning trace and stopped.
* type "kill", and it doesn't die.

At first I tried to blame gdb and checked the source, but
all it does is call kill (pid, SIGKILL), so I tried it from
the shell and sure enough, it won't die.  Its a little annoying,
I have to exit the gdb before the process will die.  Can anyone
else reproduce or explain this?

-josh