From: Joel Brobecker <brobecker@adacore.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] gdb.base a*.exp b*.exp send_gdb vs gdb_test
Date: Wed, 26 May 2010 17:51:00 -0000 [thread overview]
Message-ID: <20100526174659.GC3019@adacore.com> (raw)
In-Reply-To: <4BFD5CA5.9070605@vmware.com>
> No, it's the regexp. It ends with "$gdb_prompt$", with no trailing
> space. gdb_test requires the output to end with "$gdb_prompt $",
> including the trailing space.
>
> Subtle but critical. ;-))
Subtle indeed. So the GDB prompt does not have a trailing space
in this testcase? If that's the case, then no other observation
(and OK to commit).
--
Joel
next prev parent reply other threads:[~2010-05-26 17:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 22:04 Michael Snyder
2010-05-26 17:38 ` Joel Brobecker
2010-05-26 17:41 ` Michael Snyder
2010-05-26 17:51 ` Joel Brobecker [this message]
2010-05-26 21:59 ` Michael Snyder
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=20100526174659.GC3019@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.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