From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27656 invoked by alias); 6 Oct 2009 10:53:34 -0000 Received: (qmail 27641 invoked by uid 48); 6 Oct 2009 10:53:34 -0000 Date: Tue, 06 Oct 2009 10:53:00 -0000 Message-ID: <20091006105334.27640.qmail@sourceware.org> From: "pedro at codesourcery dot com" To: gdb-prs@sourceware.org In-Reply-To: <20091006104401.10737.pedro@codesourcery.com> References: <20091006104401.10737.pedro@codesourcery.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug gdb/10737] catch syscall name mappings (xml) should be per-arch or per-target, not global X-Bugzilla-Reason: CC Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org X-SW-Source: 2009-q4/txt/msg00023.txt.bz2 ------- 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.