[Bug gdb/10737] New: catch syscall name mappings (xml) should be per-arch or per-target, not global

["pedro at codesourcery dot com" <sourceware-bugzilla at sourceware dot org>]

The syscall file and the syscall name mappings aren't associated with
the target or with gdbarch, they're global.  This means that e.g., a
gdb configured with native linux debugging support, connected to
a non-linux remote target, or to a linux remote target or a different
arch (hence different syscall name mappings) than the native
target mistakenly uses the native gdb target's syscall name mapping.

-- 
           Summary: catch syscall name mappings (xml) should be per-arch or
                    per-target, not global
           Product: gdb
           Version: 6.50
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: gdb
        AssignedTo: unassigned at sourceware dot org
        ReportedBy: pedro at codesourcery dot com
                CC: gdb-prs at sourceware dot org


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.