From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Yao Qi <yao@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix PR16508
Date: Wed, 05 Mar 2014 20:33:00 -0000 [thread overview]
Message-ID: <53178A28.8060206@redhat.com> (raw)
In-Reply-To: <87lhwo76qv.fsf@fleche.redhat.com>
On 03/05/2014 08:03 PM, Tom Tromey wrote:
> Yao> +if [prepare_for_testing $expfile $executable $srcfile \
> Yao> + [list debug]] {
> Yao> + untested "failed to prepare for trace tests"
>
> prepare calls untested for you, so no need to do it again.
Note that the first argument to prepare_for_testing is
what is passed to untested (and really only used for that),
so a better alternative even is to do:
if [prepare_for_testing "failed to prepare for trace tests" \
$executable $srcfile [list debug]] {
Although we do that all over the place, passing $expfile
to untested is useless, as that information will be
in the gdb.sum before UNTESTED anyway.
I'd support us starting to use this pattern more.
--
Pedro Alves
next prev parent reply other threads:[~2014-03-05 20:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-15 6:58 Yao Qi
2014-03-05 2:08 ` ping: " Yao Qi
2014-03-05 20:03 ` Tom Tromey
2014-03-05 20:33 ` Pedro Alves [this message]
2014-03-06 3:39 ` Yao Qi
2014-03-06 13:35 ` Joel Brobecker
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=53178A28.8060206@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
--cc=yao@codesourcery.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