This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/19494] New: hang killing unfollowed fork children
- From: "palves at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Tue, 19 Jan 2016 16:46:05 +0000
- Subject: [Bug gdb/19494] New: hang killing unfollowed fork children
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=19494
Bug ID: 19494
Summary: hang killing unfollowed fork children
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: palves at redhat dot com
Target Milestone: ---
If you run to a fork catchpoint, and at that point kill the parent, gdb will
kill the child as well. However, if before you resume any other thread, you
try to kill another process, gdb hangs, trying to kill the same process that is
already gone:
(gdb) catch fork
Catchpoint 2 (fork)
...
(gdb) continue
Continuing.
[New process 32079]
Thread 2.1 "catch-fork-kill" hit Catchpoint 2 (forked process 32080),
0x0000003615ebc7cc in __libc_fork () at
../nptl/sysdeps/unix/sysv/linux/fork.c:130
130 pid = ARCH_FORK ();
(gdb) kill inferior 2
(gdb) kill inferior 1
*hang*
--
You are receiving this mail because:
You are on the CC list for the bug.