The following reply was made to PR gdb/2078; it has been noted by GNATS.
From: Daniel Jacobowitz <drow@xxxxxxxxx>
To: Markus Schiltknecht <markus@xxxxxxxxxx>
Cc: gdb-gnats@xxxxxxxxxxxxxxxxxx
Subject: Re: gdb/2078: GNU/Linux, x86, catchpoint hit fork returns wrong pid on
heavy load
Date: Tue, 7 Feb 2006 13:17:25 -0500
On Tue, Feb 07, 2006 at 07:14:38PM +0100, Markus Schiltknecht wrote:
> > Of course, you can't attach another GDB to the PIDs gdb reports! When
> > it reports them, it's still attached to them.
>
> Even if 'detach-on-fork' is on? That explains the ptrace error I got,
> thank you for clarification of this related problem.
Right. This is a little subtle. When GDB stops and tells you that a
fork has occurred, you still have the option to follow the parent or
the child; it's not until you resume one of them that GDB lets go of
the other.
(And it's slightly more complicated than that for vfork.)
--
Daniel Jacobowitz
CodeSourcery
|
