From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19405 invoked by alias); 29 Mar 2012 14:43:50 -0000 Received: (qmail 19318 invoked by uid 22791); 29 Mar 2012 14:43:49 -0000 X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 29 Mar 2012 14:43:32 +0000 Received: from svr-orw-exc-10.mgc.mentorg.com ([147.34.98.58]) by relay1.mentorg.com with esmtp id 1SDGZX-00061H-Fu from Hui_Zhu@mentor.com ; Thu, 29 Mar 2012 07:43:31 -0700 Received: from SVR-ORW-FEM-04.mgc.mentorg.com ([147.34.97.41]) by SVR-ORW-EXC-10.mgc.mentorg.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 29 Mar 2012 07:42:58 -0700 Received: from [127.0.0.1] (147.34.91.1) by svr-orw-fem-04.mgc.mentorg.com (147.34.97.41) with Microsoft SMTP Server id 14.1.289.1; Thu, 29 Mar 2012 07:43:30 -0700 Message-ID: <4F74750F.80006@mentor.com> Date: Thu, 29 Mar 2012 14:43:00 -0000 From: Hui Zhu User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120310 Thunderbird/11.0 MIME-Version: 1.0 To: Pedro Alves CC: 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> <4F742F7D.1070602@redhat.com> <4F746B2A.6000302@mentor.com> <4F746DF3.5040500@redhat.com> <4F747005.8070109@mentor.com> <4F7470E7.7030001@redhat.com> <4F7473ED.6070007@mentor.com> <4F747435.1040805@redhat.com> In-Reply-To: <4F747435.1040805@redhat.com> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit 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: 2012-03/txt/msg00998.txt.bz2 On 03/29/12 22:39, Pedro Alves wrote: > On 03/29/2012 03:38 PM, Hui Zhu wrote: > >> On 03/29/12 22:25, Pedro Alves wrote: >>> Let me put this another way. If when testing against a remote target, we find >>> ourselves testing a feature that happens to not be supported by the currently connected >>> remote target, but may be supported by the native target, do you think a test should go >>> through contortions to run against the native target? (the answer is no). >>> >> >> Yes, I know you worry about it and I agree with it. So I add TRACE_TRY_GDBSERVER. >> >> For the test that against a remote target or other normal way, because TRACE_TRY_GDBSERVER is not set. Test will not auto try target remote when current target didn't support trace. >> >> When we want test the function inside the GDB, we can set TRACE_TRY_GDBSERVER, then test will use gdbserver if need. > > > Sorry, no, we don't want to add this. Just run the testsuite against gdbserver if that's what you want to test. > That is back to the old question I ask for, right? :) Why the way try to make the trace function of GDB more easy be tested is not you want. And this way didn't affect current test. Thanks, Hui