From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4012 invoked by alias); 4 Nov 2008 15:36:33 -0000 Received: (qmail 4002 invoked by uid 22791); 4 Nov 2008 15:36:33 -0000 X-Spam-Check-By: sourceware.org Received: from igw2.br.ibm.com (HELO igw2.br.ibm.com) (32.104.18.25) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 04 Nov 2008 15:35:45 +0000 Received: from d24relay01.br.ibm.com (unknown [9.8.31.16]) by igw2.br.ibm.com (Postfix) with ESMTP id 0556617F580 for ; Tue, 4 Nov 2008 13:34:16 -0200 (BRDT) Received: from d24av01.br.ibm.com (d24av01.br.ibm.com [9.18.232.46]) by d24relay01.br.ibm.com (8.13.8/8.13.8/NCO v9.1) with ESMTP id mA4FZIk42662610 for ; Tue, 4 Nov 2008 12:35:21 -0300 Received: from d24av01.br.ibm.com (loopback [127.0.0.1]) by d24av01.br.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id mA4FZcOR031747 for ; Tue, 4 Nov 2008 13:35:39 -0200 Received: from [9.8.9.146] ([9.8.9.146]) by d24av01.br.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id mA4FZZ0N031542; Tue, 4 Nov 2008 13:35:37 -0200 Subject: Re: [PATCH 4/4] 'catch syscall' feature -- Build system, documentation and testcase From: =?ISO-8859-1?Q?S=E9rgio?= Durigan =?ISO-8859-1?Q?J=FAnior?= To: Daniel Jacobowitz Cc: Phil Muldoon , gdb-patches@sourceware.org In-Reply-To: <20081104151447.GB32619@caradoc.them.org> References: <1225773088.24532.56.camel@miki> <49100551.6010000@redhat.com> <1225810920.32321.5.camel@miki> <20081104151447.GB32619@caradoc.them.org> Content-Type: text/plain; charset=iso-8859-1 Date: Tue, 04 Nov 2008 15:36:00 -0000 Message-Id: <1225812925.32321.19.camel@miki> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 Content-Transfer-Encoding: 8bit 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/msg00034.txt.bz2 Hi Daniel, On Tue, 2008-11-04 at 10:14 -0500, Daniel Jacobowitz wrote: > 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. I don't know if I'm doing this correctly, but I already use [is_remote target] in the testcase. If this test returns true, I simply do a "continue", which (I think) skips this test and goes to the next one. If that's not correct, then I should fix it :-). Regards, -- Sérgio Durigan Júnior Linux on Power Toolchain - Software Engineer Linux Technology Center - LTC IBM Brazil