Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hui Zhu <hui_zhu@mentor.com>
To: Pedro Alves <palves@redhat.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] testsuite tfind.exp: If current target don't support trace, try gdbserver.
Date: Thu, 29 Mar 2012 09:29:00 -0000	[thread overview]
Message-ID: <4F742B75.3000408@mentor.com> (raw)
In-Reply-To: <4F742A2A.9060500@redhat.com>

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?

Thanks,
Hui


  reply	other threads:[~2012-03-29  9:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-29  9:18 Hui Zhu
2012-03-29  9:24 ` Pedro Alves
2012-03-29  9:29   ` Hui Zhu [this message]
2012-03-29  9:46     ` Pedro Alves
2012-03-29 14:02       ` Hui Zhu
2012-03-29 14:13         ` Pedro Alves
2012-03-29 14:23           ` Hui Zhu
2012-03-29 14:26             ` Pedro Alves
2012-03-29 14:39               ` Hui Zhu
2012-03-29 14:40                 ` Pedro Alves
2012-03-29 14:43                   ` Hui Zhu
2012-03-29 15:00                     ` Pedro Alves
2012-03-29 15:27                       ` 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=4F742B75.3000408@mentor.com \
    --to=hui_zhu@mentor.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.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