Hi, On Tue, Jun 07, 2016 at 05:33:07PM +0300, Samuli Seppänen wrote: > > I played with valgrind a bit > > > > https://travis-ci.org/chipitsine/openvpn/jobs/135869065 > > > > Looks like there are leaks in openssl code, should we suppress it? > > I can't comment on the leaks themselves, but I wonder if it would make > sense to run OpenVPN under Valgrind in "make check". For example, when > using the Vagrant test VMs the loss of performance would not be a big > deal - the tests would just run quite a bit longer.
Unless you can whitelist certain findings, valgrind output will be LONG
(as can be seen in the URL above), and we can't do anything about memory
lost by OpenSSL etc. - so it's just long output of random numbers, which
nobody will bother to look at.
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany g...@greenie.muc.de
fax: +49-89-35655025 g...@net.informatik.tu-muenchen.de
signature.asc
Description: PGP signature
