From: Keith Seitz <keiths@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: "gdb-patches@sourceware.org ml" <gdb-patches@sourceware.org>
Subject: Re: [RFA 3/3] Linespec rewrite: New tests
Date: Mon, 26 Mar 2012 20:35:00 -0000 [thread overview]
Message-ID: <4F70D2F2.1090604@redhat.com> (raw)
In-Reply-To: <87mx73s4om.fsf@fleche.redhat.com>
On 03/26/2012 09:33 AM, Tom Tromey wrote:
>>>>>> "Keith" == Keith Seitz<keiths@redhat.com> writes:
> If these tests all pass against CVS gdb, I think this could go in
> independently of the rewrite patch.
ls-dollar.exp does pass today, so if you would like, I can commit that
separately (now). Obviously, ls-errs.exp will not pass (as-is) because
of the error message changes. I don't see any value in adapting this
test to pass CVS HEAD.
> Keith> +set base "ls-dollar"
> Keith> +set srcfile "$base.cc"
> Keith> +set testfile "$base.exp"
> Keith> +set exefile $base
> Keith> +
> Keith> +if {[skip_cplus_tests]} {
> Keith> + unsupported linespec.exp
>
> Wrong text in the argument here.
> I think the new trend, proposed in the not-too-distant past by Pedro
> (IIRC), is to put some useful text in there instead of just the .exp
> name, since that is redundant anyhow.
Whoops. I've updated that.
> Keith> +set base ls-errs
> Keith> +set srcfile "$base.c"
> Keith> +set testfile "$base.exp"
> Keith> +set exefile $base
> Keith> +
> Keith> +if {[skip_cplus_tests]} {
> Keith> + unsupported linespec.exp
>
> Wrong text -- but there doesn't seem to be a need to examine
> skip_cplus_tests here at all.
Yeah, another cut-n-paste casualty. I've removed that and pushed both
fixes to the archer branch.
Keith
next prev parent reply other threads:[~2012-03-26 20:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 21:23 Keith Seitz
2012-03-26 18:27 ` Tom Tromey
2012-03-26 20:35 ` Keith Seitz [this message]
2012-03-26 20:48 ` Tom Tromey
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=4F70D2F2.1090604@redhat.com \
--to=keiths@redhat.com \
--cc=gdb-patches@sourceware.org \
--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