From: Pedro Alves <palves@redhat.com>
To: Hui Zhu <hui_zhu@mentor.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 14:40:00 -0000 [thread overview]
Message-ID: <4F747435.1040805@redhat.com> (raw)
In-Reply-To: <4F7473ED.6070007@mentor.com>
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.
--
Pedro Alves
next prev parent reply other threads:[~2012-03-29 14:40 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
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 [this message]
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=4F747435.1040805@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=hui_zhu@mentor.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