This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/15879] New: "catch syscall fork" doesn't do what users think it will do
- From: "dje at google dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Thu, 22 Aug 2013 18:59:24 +0000
- Subject: [Bug gdb/15879] New: "catch syscall fork" doesn't do what users think it will do
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=15879
Bug ID: 15879
Summary: "catch syscall fork" doesn't do what users think it
will do
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: dje at google dot com
On linux (at least for awhile) fork() is implemented with clone().
To people knowledgeable about unix (or newbies), but not necessarily linux,
having gdb report success for "catch syscall fork" and then "not working" is
confusing.
GDB could help the user out a bit here.
--
You are receiving this mail because:
You are on the CC list for the bug.