From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-70338-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 21161 invoked by alias); 19 Feb 2010 18:42:17 -0000
Received: (qmail 21150 invoked by uid 22791); 19 Feb 2010 18:42:16 -0000
X-SWARE-Spam-Status: No, hits=-1.3 required=5.0 	tests=AWL,BAYES_00,RCVD_IN_SORBS_WEB,SPF_SOFTFAIL
X-Spam-Check-By: sourceware.org
Received: from mtaout22.012.net.il (HELO mtaout22.012.net.il) (80.179.55.172)     by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 19 Feb 2010 18:42:11 +0000
Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0KY300A00QJS6I00@a-mtaout22.012.net.il> for gdb-patches@sourceware.org; Fri, 19 Feb 2010 20:42:08 +0200 (IST)
Received: from HOME-C4E4A596F7 ([84.228.213.68]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0KY3008UVQM7CT40@a-mtaout22.012.net.il>; Fri, 19 Feb 2010 20:42:08 +0200 (IST)
Date: Fri, 19 Feb 2010 18:42:00 -0000
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: RFA: valgrind and the test suite, take 2
In-reply-to: <m3ljep9m1j.fsf@fleche.redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Reply-to: Eli Zaretskii <eliz@gnu.org>
Message-id: <83y6ipvzlb.fsf@gnu.org>
References: <m3ljep9m1j.fsf@fleche.redhat.com>
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2010-02/txt/msg00497.txt.bz2

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