testsuite: native/non-extended/extended modes [Re: [PATCH] PR threads/10729: x86 hw watchpoints and non-stop mode]

Jan Kratochvil
2012-01-20T19:45:54Z

On Fri, 16 Dec 2011 16:16:56 +0100, Pedro Alves wrote:
> Currently, because there's no extended-remote board, the only way to
> be a bit certain that we aren't making extended-remote "attach"/"run"
> support in gdbserver a brick is the gdb.server/ tests. Let's take a
> look at what we're talking about:
>
> $ ls gdb.server/*.exp
> gdb.server/ext-attach.exp
> gdb.server/ext-run.exp
> gdb.server/file-transfer.exp
> gdb.server/server-mon.exp
> gdb.server/server-run.exp
>
> That's it. Once we have a board that tests the whole testsuite in
> extended-remote mote, the ext-*.exp tests become useless and
> redundant, and so all uses of gdbserver_start_extended can be eliminated
> -- we have plenty of regular tests that "run" and "attach". Meanwhile,
> we don't such a board, so we live with the exception that the
> tests force gdbserver, and extended-remote. This is what I mean
> by revisiting later. (I don't see a point in adding a board variable
> for "supports extended-remote" at this point.)

As I have another testcase in archer-jankratochvil-watchpoint3
gdb.multi/watchpoint-multi.exp needing extended gdbserver and you are already
working on extended-remote board could you restate what is the recommended way
how to create a testcase which:
* supports native mode
* does not support non-extended-remote
* supports extended-remote
?

Thanks,
Jan