This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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


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.

Thanks,
Hui


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]