From: Pedro Alves <pedro@codesourcery.com>
To: Marek Polacek <mpolacek@redhat.com>
Cc: gdb-patches@sourceware.org, Tom Tromey <tromey@redhat.com>
Subject: Re: [PATCH] gdb.mi/mi-nonstop.exp: fix racy tests (PR testsuite/12649)
Date: Fri, 27 May 2011 12:08:00 -0000 [thread overview]
Message-ID: <201105271308.16230.pedro@codesourcery.com> (raw)
In-Reply-To: <4DDF8F00.6030504@redhat.com>
On Friday 27 May 2011 12:46:08, Marek Polacek wrote:
> On 05/27/2011 01:20 PM, Marek Polacek wrote:
> > On 05/26/2011 06:32 PM, Pedro Alves wrote:
> >> This pattern appears in all the MI non-stop tests. It'd be nice
> >> to move it to mi-support.exp (ideally in a preparatory patch
> >> that just does the factoring/moving, and nothing else.)
> >
> > I'll do it in a bit.
>
> On the other hand, what's actually the point of setting the `supported'
> variable? The above mentioned pattern for setting the `supported'
> variable is to be found in these tests:
>
> mi-nsthrexec.exp
> mi-nonstop-exit.exp
> mi-nsintrall.exp
> mi-nsmoribund.exp
> mi-nonstop.exp
> mi-ns-stale-regcache.exp
>
> But the `supported' variable is never used beyond the "-gdb-show non-stop"
> part. What am I missing?
Eh, good question. I don't even remember that the ,supported= bit
ever existed? Patch to remove all of that is pre-approved.
--
Pedro Alves
next prev parent reply other threads:[~2011-05-27 12:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-19 10:41 Marek Polacek
2011-05-26 16:24 ` Tom Tromey
2011-05-26 16:32 ` Pedro Alves
2011-05-27 11:20 ` Marek Polacek
2011-05-27 11:46 ` Marek Polacek
2011-05-27 12:08 ` Pedro Alves [this message]
2011-05-27 12:49 ` Marek Polacek
2011-05-27 17:55 ` Tom Tromey
2011-05-27 17:56 ` Marek Polacek
2011-05-27 14:07 ` Marek Polacek
2011-05-27 14:14 ` Pedro Alves
2011-05-27 14:18 ` Marek Polacek
2011-05-27 10:58 ` Marek Polacek
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=201105271308.16230.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=mpolacek@redhat.com \
--cc=tromey@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