This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: RFA: valgrind and the test suite, take 2


> 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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]