From owner-freebsd-hackers@FreeBSD.ORG Wed May 25 18:09:35 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 202191065780 for ; Wed, 25 May 2011 18:09:35 +0000 (UTC) (envelope-from krivenok.dmitry@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id A5AB28FC08 for ; Wed, 25 May 2011 18:09:34 +0000 (UTC) Received: by bwz12 with SMTP id 12so4793bwz.13 for ; Wed, 25 May 2011 11:09:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=I+naTFv6agjzko8c4rirPq14gxz0DSd3OnJg1nhCqPA=; b=lBY2Gxsv+2M0sOUja51QvZU8icGT2l81vXlQ8CNRZcU+2lhPBPEO5gPYz3nw83FMY6 Dfj0k0r5k3XYTJBrv7LAJFeDPcy8d5KqKROr9hO5Sdo/N5yhDGKhN7kKgvcTkEXGCPtk v4kVaS0YzGtgwUe0ae//FHTYJmbn2RWxVnNoA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=d7yzo00dfF16eF2j5WIf5j6DnihkMPNNd5i5cdDr54z6CXfYWqRA5R5wtbhiQ+4GNt ZZBijmSMJiUb8cFIMTD1M+TqDFgL8oeNGscUsp1yk7wWE3E1dOWIJYeqXAIt3sYg3qAS NMmIcKcakLH14+r7/Yh3ERNxSUkqMPO3NB6xg= MIME-Version: 1.0 Received: by 10.204.151.202 with SMTP id d10mr4403969bkw.168.1306345649396; Wed, 25 May 2011 10:47:29 -0700 (PDT) Received: by 10.204.85.100 with HTTP; Wed, 25 May 2011 10:47:29 -0700 (PDT) Date: Wed, 25 May 2011 21:47:29 +0400 Message-ID: From: Dmitry Krivenok To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Possible bug in gdb-6.1.1 (it leaves zombie processes) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 May 2011 18:09:35 -0000 Hello hackers, I think I found a bug in base gdb-6.1.1 on FreeBSD-8.2. Below is how you can reproduce it. I run "sleep 10" command under control of gdb-6.1.1 as follows $ gdb --args sleep 10 GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or 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. This GDB was configured as "amd64-marcel-freebsd"...(no debugging symbols found)... (gdb) r Starting program: /bin/sleep 10 (no debugging symbols found)...(no debugging symbols found)... Program exited normally. (gdb) q $ During execution of sleep I saw: $ ps auxw | grep sleep krived 2951 0.0 1.1 15836 5520 0 S 4:14PM 0:00.04 gdb --args sleep 10 krived 2952 0.0 0.2 2764 840 0 SX+ 4:14PM 0:00.01 /bin/sleep 10 $ As expected, once sleep exited and got $ ps auxw | grep sleep krived 2951 0.0 1.1 15836 5520 0 S+ 4:14PM 0:00.04 gdb --args sleep 10 $ However, I found that sleep process became a zombie: $ ps auxw | grep 2952 krived 2952 0.0 0.0 0 0 0 Z 4:14PM 0:00.01 $ Then I closed gdb and zombie process went away: $ ps auxw | grep 2952 $ I did a quick search through the Google and found that other people also encountered this problem before: https://bugzilla.redhat.com/show_bug.cgi?id=243845 I tried the same test with gdb-7.2 installed from ports and there was no zombie process. I didn't find any reports on this problem in PR database. Can this problem be classified as a bug in base gdb-6.1.1? Thanks!