This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: pending/1949: attaching to a running process then quitting leaves stale gdb processes
- From: Daniel Jacobowitz <drow at false dot org>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 26 May 2005 14:08:03 -0000
- Subject: Re: pending/1949: attaching to a running process then quitting leaves stale gdb processes
- Reply-to: Daniel Jacobowitz <drow at false dot org>
The following reply was made to PR pending/1949; it has been noted by GNATS.
From: Daniel Jacobowitz <drow@false.org>
To: gnu@greglaw.net
Cc: gdb-gnats@sources.redhat.com
Subject: Re: pending/1949: attaching to a running process then quitting leaves stale gdb processes
Date: Thu, 26 May 2005 10:05:54 -0400
On Wed, May 25, 2005 at 03:49:44PM -0000, gnu@greglaw.net wrote:
> I've noticed that when I attach gdb to a running process, then quit,
> there is a stale copy of gdb left. The process is in state T
> (stopped or ptraced).
>
> I don't see this on fedora or on Debian, only on gentoo.
It's sensitive to the kernel version and GDB patches - Debian has the
fix if it's what I think it is. Please try a CVS snapshot?
--
Daniel Jacobowitz
CodeSourcery, LLC