Re: valgrind-tests and suppression files

2020-05-23 Thread Jeffrey Walton
On Sat, May 23, 2020 at 5:40 PM Marc Nieper-Wißkirchen
 wrote:
>
> Is there any built-in support in the valgrind-tests module for
> suppression files? For example, if I want to run my tests under
> valgrind (if available), I write
>
> LOG_COMPILER = $(VALGRIND)
>
> or, in case I use libtool,
>
> LOG_COMPILER = $(LIBTOOL) --mode=execute $(VALGRIND)
>
> But how to add valgrind suppression files in this context?
>
> LOG_COMPILER = $(VALGRIND) --suppressions=...
>
> is not a good solution because it will fail when VALGRIND is empty
> because valgrind-tests couldn't find a valgrind.
>
> What's the canonical solution of this problem?

Placing Valgrind annotations in the source file so the annotations
cannot be disgorged from the source file. It also benefits users so
things "just work" for them out of the box. No reading manuals, no
crafting suppression files.

I don't know if Valgrind support has matured that far, though.

Jeff



valgrind-tests and suppression files

2020-05-23 Thread Marc Nieper-Wißkirchen
Is there any built-in support in the valgrind-tests module for
suppression files? For example, if I want to run my tests under
valgrind (if available), I write

LOG_COMPILER = $(VALGRIND)

or, in case I use libtool,

LOG_COMPILER = $(LIBTOOL) --mode=execute $(VALGRIND)

But how to add valgrind suppression files in this context?

LOG_COMPILER = $(VALGRIND) --suppressions=...

is not a good solution because it will fail when VALGRIND is empty
because valgrind-tests couldn't find a valgrind.

What's the canonical solution of this problem?