bug-libtool
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: valgrind-tests.m4


From: Ralf Wildenhues
Subject: Re: valgrind-tests.m4
Date: Thu, 20 May 2010 20:18:10 +0200
User-agent: Mutt/1.5.20 (2009-10-28)

[ adding bug-libtool ]

* Bruno Haible wrote on Wed, May 19, 2010 at 11:12:08AM CEST:
> Simon Josefsson wrote:
> > my patch invokes valgrind with -q so that it does not
> > output anything, unless there are errors, of course
> 
> Oh, I see. Indeed.
> 
> But it spends a lot of time in "make check", and does not exploit the full
> information that valgrind could provide. For a test, I ran "make check"
> in gettext/gettext-tools/tests,
> * With --enable-shared and libtool wrappers:
>   - without valgrind:                                                 105 sec.
>   - with valgrind -q for just the sh that runs the test:             1191 sec.
>   - with valgrind -q for just the sh that runs the libtool wrappers: 6457 sec.
> * Without libtool wrappers:
>   - without valgrind:                                                  42 sec.
>   - with valgrind -q for just the programs:                          2147 sec.

That's quite bad.  Maybe libtool should have a way to use valgrind only
on the "interesting" executable, not the rest of any wrappers, or the
libtool script, for efficiency reasons.

Thanks for the report.

Cheers,
Ralf



reply via email to

[Prev in Thread] Current Thread [Next in Thread]