This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Follow-fork-mode and inferiors
- From: Kevin Pouget <kevin dot pouget at gmail dot com>
- To: gdb at sourceware dot org
- Date: Wed, 13 Apr 2011 09:33:01 -0400
- Subject: Follow-fork-mode and inferiors
- References: <BANLkTikpEhjP-RPyLFcwoF=nC3K+oas-ZQ@mail.gmail.com>
Hello,
I noticed a behavior which appears strange to me, I would like to know
if it was expected:
> (gdb) list
> 1??? int main() {
> 2??? ??? fork() ;
> 3??? }
>
> (gdb) break 3
> (gdb) set follow-fork-mode child
> (gdb) run
> ...
> Breakpoint 1, main () at fork.c:3
> 3??? }
> (gdb) info inferiors
> ? Num? Description?????? Executable
> * 2??? process 26039???? /home/kevin/travail/arm/perso/root/sample/fork-threads/fork
> ? 1??? <null>??????????? /home/kevin/travail/arm/perso/root/sample/fork-threads/fork
why are there two inferiors? I expected either to stay in inf 1 (if
the pid of an inferior can change) or inf 1 to disappear, but not to
keep both of them!
thanks,
Kevin