Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <vladimir@codesourcery.com>
To: gdb-patches@sources.redhat.com
Subject: Re: Enable non-stop mode MI tests against remote targets.
Date: Thu, 02 Apr 2009 14:08:00 -0000	[thread overview]
Message-ID: <gr2grj$roa$1@ger.gmane.org> (raw)
In-Reply-To: <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



  reply	other threads:[~2009-04-02 14:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-26  1:03 Pedro Alves
2009-03-26  4:25 ` Pedro Alves
2009-04-01 23:23   ` Pedro Alves
2009-04-02 14:08     ` Vladimir Prus [this message]
2009-04-02 16:13       ` Pedro Alves

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='gr2grj$roa$1@ger.gmane.org' \
    --to=vladimir@codesourcery.com \
    --cc=gdb-patches@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox