This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Enable non-stop mode MI tests against remote targets.
- From: Vladimir Prus <vladimir at codesourcery dot com>
- To: gdb-patches at sources dot redhat dot com
- Date: Thu, 02 Apr 2009 18:07:56 +0400
- Subject: Re: Enable non-stop mode MI tests against remote targets.
- References: <200903260054.52525.pedro@codesourcery.com> <200903260228.28983.pedro@codesourcery.com> <200904020023.31264.pedro@codesourcery.com>
Pedro Alves wrote:
> On Thursday 26 March 2009 02:28:28, Pedro Alves wrote:
>> On Thursday 26 March 2009 00:54:52, Pedro Alves wrote:
>> > With this patch, the MI non-stop mode tests pass cleanly against
>> > gdbserver once the gdbserver non-stop mode patch is applied:
>> >
>> > http://sourceware.org/ml/gdb-patches/2009-03/msg00582.html
>> >
>> > The tests currently assume a native GDB. They use -exec-run
>> > directly. I've changed them to use mi_run_to_main, which
>> > works nicelly. To make the tests fails fail gracefully when
>> > the remote side doesn't support non-stop mode, I've made
>> > mi_run_to_main and its callees propagate an error return up,
>> > similarly to CLI's runto_main. This means that this patch can go
>> > in before the gdbserver bits go in. Most other MI tests could be
>> > adjusted to do the same "if { [mi_run_to_main] < 0 } { BAIL }"
>> > check, which avoids cascasted FAILs and timeouts.
>> >
>> > Vladimir, do you think this looks OK?
>
>
> Hi Vladimir, gdbserver now supports non-stop mode, so we need
> to be able to test it. :-) Do you have any comments on
> this approach?
Thanks for asking. I think it's fine!
- Volodya