Simon Josefsson <[email protected]> writes: >>> However, valgrind should not be used unless requested, so that is a bug. >>> Does that always happen for you? I've found that always using valgrind >>> when it is available causes too much problems: it is common for system >>> libraries have memory leaks, even libc. So my opinion is that it should >>> only be on for people who requested it (or build from git). >> >> Yes, it is enabled with release tarball (tested with 2.0.1) as soon as >> valgrind is installed. > > Ouch. I'll see if I can fix this.
Should be fixed now -- if you build from git you get valgrind enabled when present by default, if you build from tarballs you don't. /Simon
