From owner-freebsd-hackers Sun Feb 23 03:15:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id DAA04889 for hackers-outgoing; Sun, 23 Feb 1997 03:15:21 -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 DAA04884 for ; Sun, 23 Feb 1997 03:15:18 -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 DAA16417 for ; Sun, 23 Feb 1997 03:15:17 -0800 (PST) From: Josh MacDonald Message-Id: <199702231115.DAA16417@paris.CS.Berkeley.EDU> To: freebsd-hackers@freebsd.org Subject: more on killing traced processes MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <16410.856696513.1@paris.CS.Berkeley.EDU> Date: Sun, 23 Feb 1997 03:15:15 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Sorry for giving so little info. Jordan replied off list with an example of how not to show this behaviour, so I'll provide an example. Run gdb on /bin/cat: Current directory is /bin/ GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc... (no debugging symbols found)... (gdb) run Starting program: /bin/cat Program received signal SIGINT, Interrupt. 0xe7b5 in ?? () (gdb) kill Kill the program being debugged? (y or n) y (gdb) A second attempt to kill from gdb reports, "The program is not being run." Investigation from 'ps' output shows that the /bin/cat process is still running, in the TX state. Running "kill -9 PID" will not kill the process. Only when the parent exits can it die. -josh