From: Tom Tromey <tromey@redhat.com>
To: Keith Seitz <keiths@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 18:27:00 -0000 [thread overview]
Message-ID: <87mx73s4om.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4F67A3B3.6030500@redhat.com> (Keith Seitz's message of "Mon, 19 Mar 2012 14:22:59 -0700")
>>>>> "Keith" == Keith Seitz <keiths@redhat.com> writes:
Keith> This final patch, also dealing with testing, introduces several new
Keith> tests. While one or two of these add tests for new features, several
Keith> just add missing tests, like "break ::foo" (surprisingly /not/ tested
Keith> today).
This looks pretty good.
If these tests all pass against CVS gdb, I think this could go in
independently of the rewrite patch.
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.
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.
Tom
next prev parent reply other threads:[~2012-03-26 18:27 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 [this message]
2012-03-26 20:35 ` Keith Seitz
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=87mx73s4om.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@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