Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Marek Polacek <mpolacek@redhat.com>
Cc: Tom Tromey <tromey@redhat.com>,  gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb.base/setshow.exp: fix racy tests (PR testsuite/12649)
Date: Tue, 19 Apr 2011 13:48:00 -0000	[thread overview]
Message-ID: <m2bp02fj2i.fsf@igel.home> (raw)
In-Reply-To: <4DAD8C40.30703@redhat.com> (Marek Polacek's message of "Tue, 19	Apr 2011 15:21:04 +0200")

Marek Polacek <mpolacek@redhat.com> writes:

> On 04/19/2011 02:52 PM, Tom Tromey wrote:
>> Maybe gdb.log says something, or maybe running with --verbose would
>> help.
>
> The `runtest -v -v -v gdb.base/setshow.exp' says this:
>
> Looking to match ""[\r\n]*(Input and output radices now set to decimal 16, hex
> 10, octal 20..*)[\r\n]+\(gdb\) $"; "(^FOOBAR$)$""
>
> Note those '\' around (gdb).

That's because it's a regexp, of course.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


  reply	other threads:[~2011-04-19 13:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-18 16:39 Marek Polacek
2011-04-18 20:46 ` Tom Tromey
2011-04-19  7:01   ` Marek Polacek
2011-04-19 10:19     ` Andreas Schwab
2011-04-19 10:31       ` Marek Polacek
2011-04-19 12:52     ` Tom Tromey
2011-04-19 13:21       ` Marek Polacek
2011-04-19 13:48         ` Andreas Schwab [this message]
2011-04-19 18:47         ` Tom Tromey
2011-04-19 19:11           ` Marek Polacek
2011-04-19 20:28             ` Andreas Schwab
2011-04-20 11:25               ` Marek Polacek
2011-04-20 13:54                 ` Tom Tromey
2011-04-20 14: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=m2bp02fj2i.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --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