From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18924 invoked by alias); 28 Feb 2013 07:16:51 -0000 Received: (qmail 18911 invoked by uid 22791); 28 Feb 2013 07:16:49 -0000 X-SWARE-Spam-Status: No, hits=-4.8 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from mail-bk0-f43.google.com (HELO mail-bk0-f43.google.com) (209.85.214.43) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 28 Feb 2013 07:16:44 +0000 Received: by mail-bk0-f43.google.com with SMTP id jm19so674540bkc.30 for ; Wed, 27 Feb 2013 23:16:43 -0800 (PST) X-Received: by 10.204.155.154 with SMTP id s26mr1783348bkw.129.1362035803087; Wed, 27 Feb 2013 23:16:43 -0800 (PST) MIME-Version: 1.0 Received: by 10.205.83.135 with HTTP; Wed, 27 Feb 2013 23:16:02 -0800 (PST) In-Reply-To: References: From: Hui Zhu Date: Thu, 28 Feb 2013 07:16:00 -0000 Message-ID: Subject: Re: [Discussion] add a build option for test to gdbserver To: Doug Evans Cc: gdb , sanimir.agovic@intel.com, Stan Shebs Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2013-02/txt/msg00093.txt.bz2 On Wed, Feb 27, 2013 at 1:28 AM, Doug Evans wrote: > On Tue, Feb 19, 2013 at 8:40 AM, Hui Zhu wrote: >> Hi guys, >> >> There are more and more function add to the target remote to support >> different gdbstub. >> Some of them can add a this function to gdbserver. Then the testsuite >> for it can just test with gdbserver. For example: tracepoint. >> >> But some function is hard to achieve or not very useful for gdbsever. >> I just work on some patches just have this function for example: TD >> breakpoint. TA. >> So I suggest what about add a build option for test to gdbserver? this >> option just for test. >> It maybe just send some fake package back to GDB remote or something. >> Then we can easier write test for this remote patches. > > Hi. I think you need to elaborate. > > Setting aside unittests that can test individual pieces of gdb/gdbserver, > something has to talk to gdbserver in order to test it, > and there is testsuite/gdb.server for gdbserver specific tests. Hi Doug, Thanks for your remind. I think I should talk it clear in the title. I think it should be "Add a build option that test remote target to gdbserver". What about it? And there is some thought of me: To test remote target, we add them to gdbserver and use a build option control. And when we build gdbserver, we can build 2 gdbserver. One is just to use, and named it as "gdbserver". Others is just for test, and named it as "gdbservertest". Thanks, Hui