This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Problems debugging forked processes
On Sun, Apr 21, 2002 at 09:12:33AM +0300, Eli Zaretskii wrote:
>
> On Fri, 19 Apr 2002, Daniel Jacobowitz wrote:
>
> > > (gdb) show follow-fork-mode
> > > Debugger response to a program call of fork or vfork is "parent".
> > > (gdb) set follow-fork-mode child
> > > (gdb) show follow-fork-mode
> > > Debugger response to a program call of fork or vfork is "child".
> >
> > This variable doesn't actually affect GNU/Linux. Yeah, I know, I know.
> > We need a documentation patch to address this; please file a PR
> > (http://sources.redhat.com/gdb/, Bugs).
>
> If someone tells me what should be documented, I'll do that. Now is the
> time, since v5.2 is in pretest.
>
> Is the issue that follow-fork-mode is only supported on a small number of
> systems? If so, what are those systems, and is it enough to have their
> list in the manual?
I believe the only platform to implement this is actually HP/UX:
drow@nevyn:/opt/src/gdb/src/gdb% grep -r CHILD_HAS_FORKED .
./inftarg.c:#if !defined(CHILD_HAS_FORKED)
./config/pa/nm-hppah.h:#define CHILD_HAS_FORKED
./infttrace.c:#if defined(CHILD_HAS_FORKED)
./ChangeLog-1998: (child_has_forked): Now enclosed by a CHILD_HAS_FORKED ifdef
There's a nice new debugging interface in the works for GNU/Linux that
will let us support this some day. But for now, HP/UX only.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer