This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug breakpoints/13457] New: `catch syscall' doesn't work after`fork' is called
- From: "sergiodj at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Tue, 29 Nov 2011 19:48:36 +0000
- Subject: [Bug breakpoints/13457] New: `catch syscall' doesn't work after`fork' is called
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=13457
Bug #: 13457
Summary: `catch syscall' doesn't work after `fork' is called
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: breakpoints
AssignedTo: unassigned@sourceware.org
ReportedBy: sergiodj@redhat.com
Classification: Unclassified
Given this simple example:
#include <stdio.h>
#include <unistd.h>
int
main (int argc, char **argv)
{
if (fork () == 0)
printf ("Child\n");
chdir (".");
return 0;
}
When a syscall catchpoint for `chdir' is inserted, GDB does not stop and the
program runs until the end.
However, if we set `follow-fork-mode' to `child', then the catchpoint triggers
correctly.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.