Re: [PATCH] testsuite tfind.exp: If current target don't support trace, try gdbserver.

[Hui Zhu <hui_zhu@mentor.com>]

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