From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: valgrind and the test suite, take 2
Date: Fri, 19 Feb 2010 18:42:00 -0000 [thread overview]
Message-ID: <83y6ipvzlb.fsf@gnu.org> (raw)
In-Reply-To: <m3ljep9m1j.fsf@fleche.redhat.com>
> From: Tom Tromey <tromey@redhat.com>
> Date: Fri, 19 Feb 2010 10:23:52 -0700
>
> +@item @code{VALGRIND}
> +
> +It is useful to occasionally run @value{GDBN} under @code{valgrind},
> +to find bugs that do not always result in an immediate failure. This
> +can be accomplished by setting @code{VALGRIND}. The contents of this
> +will be appended to the internal @code{valgrind} command line that the
> +test suite computes. @code{VALGRIND} can be empty.
This does not explain what could be the value of VALGRIND. I needed
to read it several times before I realized that it should be a string
specifying various options and switches to the `valgrind' command. So
how about this alternative wording:
It is occasionally useful to run the @value{GDBN} test suite under
@command{valgrind}, to find bugs that do not always result in an
immediate failure of one of the tests. This can be accomplished by
setting @code{VALGRIND}. The value should be a string specifying
non-default command-line arguments and options to be passed to
@code{valgrind}; it will be appended to the internal @code{valgrind}
command line that the test suite computes. An empty string causes
the tests to be run under @command{valgrind} without modifying its
command line.
prev parent reply other threads:[~2010-02-19 18:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-19 17:24 Tom Tromey
2010-02-19 17:45 ` Pedro Alves
2010-02-19 18:09 ` Joel Brobecker
2010-02-19 19:34 ` Pedro Alves
2010-02-19 20:24 ` Joel Brobecker
2010-02-19 20:02 ` Tom Tromey
2010-02-19 20:28 ` Pedro Alves
2010-02-19 21:09 ` Tom Tromey
2010-02-19 21:27 ` Pedro Alves
2010-02-19 18:42 ` Eli Zaretskii [this message]
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=83y6ipvzlb.fsf@gnu.org \
--to=eliz@gnu.org \
--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