This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/10737] catch syscall name mappings (xml) should be per-arch or per-target, not global
- From: "pedro at codesourcery dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: 6 Oct 2009 10:53:34 -0000
- Subject: [Bug gdb/10737] catch syscall name mappings (xml) should be per-arch or per-target, not global
- References: <20091006104401.10737.pedro@codesourcery.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From pedro at codesourcery dot com 2009-10-06 10:53 -------
This isn't that a big deal currently, it's more a design issue,
as only the linux native target catching syscalls
as of 7.0. To reproduce this, I guess one only needs to
start with a --enable-targets=all gdb, and do:
$ gdb ./my_cross_binary_of_some_random_architecture_not_the_native
(gdb) catch syscall 123
<123 will be mapped using the native target's syscall mappings>
I think currently GDB will then error out when the user connects
to the remote end with "target remote", since the remote target
doesn't support target_set_syscall_catchpoint.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed| |1
http://sourceware.org/bugzilla/show_bug.cgi?id=10737
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.