From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29357 invoked by alias); 4 Nov 2008 15:16:31 -0000 Received: (qmail 23356 invoked by uid 22791); 4 Nov 2008 15:15:18 -0000 Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 04 Nov 2008 15:14:49 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 96E8510CE2; Tue, 4 Nov 2008 15:14:47 +0000 (GMT) Received: from caradoc.them.org (209.195.188.212.nauticom.net [209.195.188.212]) by nan.false.org (Postfix) with ESMTP id 8616410C35; Tue, 4 Nov 2008 15:14:47 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1KxNcF-0000sj-7R; Tue, 04 Nov 2008 10:14:47 -0500 Date: Tue, 04 Nov 2008 15:16:00 -0000 From: Daniel Jacobowitz To: =?iso-8859-1?Q?S=E9rgio_Durigan_J=FAnior?= Cc: Phil Muldoon , gdb-patches@sourceware.org Subject: Re: [PATCH 4/4] 'catch syscall' feature -- Build system, documentation and testcase Message-ID: <20081104151447.GB32619@caradoc.them.org> Mail-Followup-To: =?iso-8859-1?Q?S=E9rgio_Durigan_J=FAnior?= , Phil Muldoon , gdb-patches@sourceware.org References: <1225773088.24532.56.camel@miki> <49100551.6010000@redhat.com> <1225810920.32321.5.camel@miki> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1225810920.32321.5.camel@miki> User-Agent: Mutt/1.5.17 (2008-05-11) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-11/txt/msg00031.txt.bz2 On Tue, Nov 04, 2008 at 01:01:59PM -0200, Sérgio Durigan Júnior wrote: > > My only other comment is how this would work on remote targets (i.e. > > remote target is x86, but your host is PPC). > > To be completely honest, I still don't know the answer to this question. > I'd be glad if some good soul could try to answer this, so that I can > fix things if needed. Your patch relies on a change to the native file, right? If so, it will never trigger on remote. In order for it to trigger, we'd need: - a new remote protocol extension in gdb.texinfo - remote.c implementation - gdbserver implementation It shouldn't be too hard for someone to add it later. So restricting the tests to native targets would be enough. Search for [is_remote target] in the testsuite. -- Daniel Jacobowitz CodeSourcery