public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "sergiodj at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug breakpoints/13457] New: `catch syscall' doesn't work after `fork' is called Date: Tue, 29 Nov 2011 19:48:00 -0000 [thread overview] Message-ID: <bug-13457-4717@http.sourceware.org/bugzilla/> (raw) 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.
next reply other threads:[~2011-11-29 19:48 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-11-29 19:48 sergiodj at redhat dot com [this message] 2011-11-29 19:49 ` [Bug breakpoints/13457] `catch syscall' doesn't work for parent " sergiodj at redhat dot com 2012-10-24 16:17 ` palves at redhat dot com 2014-10-03 19:45 ` sergiodj at redhat dot com 2014-10-06 12:41 ` palves at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-13457-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).