From: Tom Tromey <tromey@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: valgrind -vs- the testsuite
Date: Fri, 10 Jul 2009 18:02:00 -0000 [thread overview]
Message-ID: <m3ocrs1ms0.fsf@fleche.redhat.com> (raw)
In-Reply-To: <e394668d0907091644j42f4954m9a17f127405c1052@mail.gmail.com> (Doug Evans's message of "Thu\, 9 Jul 2009 16\:44\:29 -0700")
>>>>> "Doug" == Doug Evans <dje@google.com> writes:
Doug> I always just use:
Doug> cd testsuite && runtest --tool gdb GDB="valgrind ../gdb"
Doug> or make check RUNTESTFLAGS='"valgrind ../gdb"'
Doug> (suitably augmented as desired),
Good point. I'm dropping this one.
Tom
next prev parent reply other threads:[~2009-07-10 17:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 18:02 Tom Tromey
2009-07-09 19:29 ` Eli Zaretskii
2009-07-10 6:35 ` Doug Evans
2009-07-10 18:02 ` Tom Tromey [this message]
2009-07-16 20:38 ` Joel Brobecker
2009-07-17 0:24 ` Tom Tromey
2009-07-20 1:17 ` Samuel Bronson
2009-07-20 5:18 ` Thiago Jung Bauermann
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=m3ocrs1ms0.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
/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