This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/9802] New: Failed to find new fork
- From: "uri at 4refs dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: 29 Jan 2009 21:23:53 -0000
- Subject: [Bug gdb/9802] New: Failed to find new fork
- Reply-to: sourceware-bugzilla at sourceware dot org
Haven't seen this on newer versions yet. This was running a very large process
(~100GB) on a machine with 132GB physical memory and 293GB swap space so perhaps
the machine just ran out of virtual memory (there are some other processes on
it). I think someone should just confirm that this is a possible scenario.
(gdb) info checkpoints
2 process 13667 at 0x7ec9b7, file <removed>, line <removed>
1 process 31468 at 0x7eb9ec, file <removed>, line <removed>
0 process 18812 (main process) at 0x92ee7c, file <removed>, line <removed>
(gdb) restart 2
Switching to process 13667
#0 <removed> (<removed>) at <removed>
(gdb) <some prints>
(gdb) restart 0
Switching to process 18812
#0 <removed> (<removed>) at <removed>
(gdb) <some prints>
(gdb) restart 2
Switching to process 13667
#0 <removed> (<removed>) at <removed>
(gdb) <some prints>
(gdb) checkpoint
checkpoint: fork returned pid -1.
Failed to find new fork
--
Summary: Failed to find new fork
Product: gdb
Version: 6.6
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdb
AssignedTo: unassigned at sourceware dot org
ReportedBy: uri at 4refs dot com
CC: gdb-prs at sourceware dot org
http://sourceware.org/bugzilla/show_bug.cgi?id=9802
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.