This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/9585] GNU/Linux x86, gdb freezes after fork wit detach-on-fork off and follow-fork-mode child
- From: "flavio dot etrusco at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: 8 Apr 2010 01:25:16 -0000
- Subject: [Bug gdb/9585] GNU/Linux x86, gdb freezes after fork wit detach-on-fork off and follow-fork-mode child
- References: <20080721155802.9585.aviseldom@infonegocio.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From flavio dot etrusco at gmail dot com 2010-04-08 01:25 -------
Thanks for the tip on "set schedule-multiple on", I've been looking for a
setting like this for quite some time in the documentation(s).
But I anyway, trying gdb behavior seems erratic, not even running the child process.
Also, unfortunately the option didn't fix the problem for me.
> Did you have "catch fork"/"catch vfork" set?
No.
> If the inferior exited, then it will have no process id, hence <null>.
Sure.
>> gdb says they have no threads.
> If the program isn't running anymore, it can't have any threads.
I meant the other inferiors, 1 and 2, not the exited inferior 3.
> I think most of your problems will go away with "set schedule-multiple on".
I'll attach the session (should have done it before...).
Thanks.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=9585
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.