Bug 15879 - "catch syscall fork" doesn't do what users think it will do
Summary: "catch syscall fork" doesn't do what users think it will do
Status: NEW
Alias: None
Product: gdb
Classification: Unclassified
Component: gdb (show other bugs)
Version: HEAD
: P2 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-22 18:59 UTC by dje
Modified: 2013-11-04 05:11 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description dje 2013-08-22 18:59:24 UTC 
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.
Comment 1 Tom Tromey 2013-10-31 20:07:02 UTC 
It would be nice to implement the same scheme that strace uses here,
to name related groups of syscalls.  Perhaps identically to strace.