Bug#849517: The valgrind diagnostic is a false positive

On 14 April 2017 at 13:47, Florian Weimer wrote: > * Reuben Thomas: > > > ​A workaround is to build bash with --without-bash-malloc (but I presume > > there's a good reason not to do that?).​ > > FWIW, Fedora and Red Hat Enterprise Linux compile bash this way, so it > can't

Bug#849517: The valgrind diagnostic is a false positive

* Reuben Thomas: > ​A workaround is to build bash with --without-bash-malloc (but I presume > there's a good reason not to do that?).​ FWIW, Fedora and Red Hat Enterprise Linux compile bash this way, so it can't be *that* bad.

Bug#849517: The valgrind diagnostic is a false positive

See: https://bugs.kde.org/show_bug.cgi?id=378732 https://lists.gnu.org/archive/html/bug-bash/2017-04/msg00042.html ​The problem, in short, is that valgrind does not intercept the malloc call (which is made via bash's built-in malloc), but does intercept the free call, and hence concludes that