Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Hui Zhu <teawater@gmail.com>
Cc: gdb <gdb@sourceware.org>,
	sanimir.agovic@intel.com, 	Stan Shebs <stan_shebs@mentor.com>
Subject: Re: [Discussion] add a build option for test to gdbserver
Date: Tue, 26 Feb 2013 17:28:00 -0000	[thread overview]
Message-ID: <CADPb22SYWBRd==14+q-DZgU2qSaTjXRo_fxLS2e_K=8FH4GD3g@mail.gmail.com> (raw)
In-Reply-To: <CANFwon2x4gJ2HT56_CH_wQSp4iWFBz5OY2JogvEHwc1ekXAWkg@mail.gmail.com>

On Tue, Feb 19, 2013 at 8:40 AM, Hui Zhu <teawater@gmail.com> 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.


  reply	other threads:[~2013-02-26 17:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-19 16:41 Hui Zhu
2013-02-26 17:28 ` Doug Evans [this message]
2013-02-28  7:16   ` Hui Zhu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADPb22SYWBRd==14+q-DZgU2qSaTjXRo_fxLS2e_K=8FH4GD3g@mail.gmail.com' \
    --to=dje@google.com \
    --cc=gdb@sourceware.org \
    --cc=sanimir.agovic@intel.com \
    --cc=stan_shebs@mentor.com \
    --cc=teawater@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox