Re: [PATCH v2] Add autoload-breakpoints [2/6] ReportAsync-test

[Hui Zhu <teawater@gmail.com>]

On Tue, May 8, 2012 at 4:39 PM, Yao Qi <yao@codesourcery.com> wrote:
> On 05/08/2012 03:26 PM, Hui Zhu wrote:
>>> Remote feature should be tested in remote target or board file.
>>> You are testing a remote feature GDB unconditionally, even in native
>>> gdb.  It looks incorrect to me.
>>>
>>
>> This just a check for the this small gdbserver is OK.   I don't think this test will work with board or something.
>>
>
> My point is this test case exercises some "undesired" features w.r.t.
> testsuite and config.  I configure and build a native gdb, and type
> `make -k check' in gdb build dir.  Then, I'll examine the FAILs in
> gdb.sum to see the status of native gdb, what does the FAILs, if any, in
> gdb.remote/reportasync-test.exp mean to me?  It sounds like "I did a
> medical check-up to my eyes, but result tells me something wrong in my
> ears".  However, I am not strongly against this test case.

Sorry I didn't get your point.  This test is for the GDB, but not for
others, right?  :)

>
> We have a sub-dir gdb.server under testsuite/, *.exp are run even when
> testing native gdb, but they are test cases to GDBserver, rather than
> GDB, AFAICS.  When we see some FAILs in it, that means GDBserver has
> something wrong, at least ideally :)

All of them are for the gdbserver.  But this test is not for
GDBserver.  If you think this dir is OK, I will move it.

When gdbserver support some function that use report-async, we can add
a new test for that.

Thanks,
Hui