This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug breakpoints/13457] `catch syscall' doesn't work for parent after `fork' is called
- From: "tromey at sourceware dot org" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Sun, 20 Aug 2017 03:50:11 +0000
- Subject: [Bug breakpoints/13457] `catch syscall' doesn't work for parent after `fork' is called
- Auto-submitted: auto-generated
- References: <bug-13457-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=13457
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
--- Comment #4 from Tom Tromey <tromey at sourceware dot org> ---
The theory in bug 17549, and in linespec, is that breakpoints should apply
to all inferiors. However, for "catch syscall", there is the additional
wrinkle that the syscall tables are OS- and architecture-dependent.
Maybe syscall catching should be per-architecture?
Right now it is per-inferior, but this seems a bit incorrect.
Another possibility might be to have a given "catch syscall"
automatically apply to any inferior where the arguments are valid
(re-translating syscall names as appropriate).
--
You are receiving this mail because:
You are on the CC list for the bug.