public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug gdb/15879] New: "catch syscall fork" doesn't do what users think it will do
@ 2013-08-22 18:59 dje at google dot com
2013-10-31 20:07 ` [Bug gdb/15879] " tromey at redhat dot com
2013-11-04 5:11 ` sergiodj at redhat dot com
0 siblings, 2 replies; 3+ messages in thread
From: dje at google dot com @ 2013-08-22 18:59 UTC (permalink / raw)
To: gdb-prs
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug gdb/15879] "catch syscall fork" doesn't do what users think it will do
2013-08-22 18:59 [Bug gdb/15879] New: "catch syscall fork" doesn't do what users think it will do dje at google dot com
@ 2013-10-31 20:07 ` tromey at redhat dot com
2013-11-04 5:11 ` sergiodj at redhat dot com
1 sibling, 0 replies; 3+ messages in thread
From: tromey at redhat dot com @ 2013-10-31 20:07 UTC (permalink / raw)
To: gdb-prs
http://sourceware.org/bugzilla/show_bug.cgi?id=15879
Tom Tromey <tromey at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at redhat dot com
--- Comment #1 from Tom Tromey <tromey at redhat dot com> ---
It would be nice to implement the same scheme that strace uses here,
to name related groups of syscalls. Perhaps identically to strace.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug gdb/15879] "catch syscall fork" doesn't do what users think it will do
2013-08-22 18:59 [Bug gdb/15879] New: "catch syscall fork" doesn't do what users think it will do dje at google dot com
2013-10-31 20:07 ` [Bug gdb/15879] " tromey at redhat dot com
@ 2013-11-04 5:11 ` sergiodj at redhat dot com
1 sibling, 0 replies; 3+ messages in thread
From: sergiodj at redhat dot com @ 2013-11-04 5:11 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=15879
Sergio Durigan Junior <sergiodj at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sergiodj at redhat dot com
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2013-11-04 5:11 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-08-22 18:59 [Bug gdb/15879] New: "catch syscall fork" doesn't do what users think it will do dje at google dot com
2013-10-31 20:07 ` [Bug gdb/15879] " tromey at redhat dot com
2013-11-04 5:11 ` sergiodj at redhat dot com
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).