From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11836 invoked by alias); 29 Mar 2012 09:46:59 -0000 Received: (qmail 11819 invoked by uid 22791); 29 Mar 2012 09:46:56 -0000 X-SWARE-Spam-Status: No, hits=-6.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 29 Mar 2012 09:46:42 +0000 Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q2T9kcri006129 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 29 Mar 2012 05:46:39 -0400 Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id q2T9kbet017275; Thu, 29 Mar 2012 05:46:38 -0400 Message-ID: <4F742F7D.1070602@redhat.com> Date: Thu, 29 Mar 2012 09:46:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120316 Thunderbird/11.0 MIME-Version: 1.0 To: Hui Zhu CC: Pedro Alves , gdb-patches@sourceware.org Subject: Re: [PATCH] testsuite tfind.exp: If current target don't support trace, try gdbserver. References: <4F7428BD.30408@mentor.com> <4F742A2A.9060500@redhat.com> <4F742B75.3000408@mentor.com> In-Reply-To: <4F742B75.3000408@mentor.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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: 2012-03/txt/msg00983.txt.bz2 On 03/29/2012 10:29 AM, Hui Zhu wrote: > On 03/29/12 17:23, Pedro Alves wrote: >> On 03/29/2012 10:17 AM, Hui Zhu wrote: >> >>> Hi, >>> >>> When we want to test the trace function that in gdb.trace directory, we will got a lot of UNSUPPORTED. To use this testcase, we need follow way in http://sourceware.org/gdb/wiki/TestingGDB#Testing_gdbserver_in_a_native_configuration. >>> >>> So I post a patch add some code if current target don't support trace, try gdbserver in tfind.exp. >>> If this patch goes OK. I will post patch for other testsuite that support by gdbserver. >> >> >> NAK. If the current target doesn't support tracing, the right thing to >> do is to skip the test, as we do currently. >> > > That is because it didn't use target remote, most trace function is together with target remote, right? There are of course remote targets that also don't support tracing. Not all GDBserver ports support tracing, or we could even be testing against a server other than GDBserver (qemu, for example). Technically, native targets could also support tracing. See e.g., Yao's push towards using an IPA with the native target. -- Pedro Alves