public inbox for dwz@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Tom de Vries <tdevries@suse.de>
Cc: dwz@sourceware.org, jakub@redhat.com
Subject: Re: [PATCH] Add check-valgrind
Date: Thu, 25 Mar 2021 21:32:54 +0100	[thread overview]
Message-ID: <20210325203254.GG2685@wildebeest.org> (raw)
In-Reply-To: <20210325135716.GA10490@delia>

Hi,

On Thu, Mar 25, 2021 at 02:57:17PM +0100, Tom de Vries wrote:
> Add a make target check-valgrind, that applies valgrind to dwz when used in
> the testsuite.
> 
> Any comments?

It might be good to simply always run under valgrind when it is
installed. That makes make check slightly slower by default, but it
makes sure things are always also ran under valgrind if available.

To make sure that a valgrind tool error really causes a check failure use
--error-exitcode=99 (or some other non-zero code):

   --error-exitcode=<number> [default: 0]
       Specifies an alternative exit code to return if Valgrind reported
       any errors in the run. When set to the default value (zero), the
       return value from Valgrind will always be the return value of the
       process being simulated. When set to a nonzero value, that value is
       returned instead, if Valgrind detects any errors. This is useful
       for using Valgrind as part of an automated test suite, since it
       makes it easy to detect test cases for which Valgrind has reported
       errors, just by inspecting return codes.

Cheers,

Mark

  reply	other threads:[~2021-03-25 20:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-25 13:57 Tom de Vries
2021-03-25 20:32 ` Mark Wielaard [this message]
2021-03-26  7:09   ` Tom de Vries

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=20210325203254.GG2685@wildebeest.org \
    --to=mark@klomp.org \
    --cc=dwz@sourceware.org \
    --cc=jakub@redhat.com \
    --cc=tdevries@suse.de \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).