Re: Running bash under valgrind gives "invalid free()"

[Hanno Böck]

On Wed, 12 Apr 2017 14:59:26 +0100
Reuben Thomas <rrt@sc3d.org> wrote:

> ​frequently, it's the only tool that shows up bugs of this sort, as
> it's rather more powerful than a debugging malloc library.)

Try address sanitizer, it's pretty reliable and finds even more bug
classes compared to valgrind. Just add -fsanitize=address to the CFLAGS.

If you can't reproduce the bug with asan I'd bet on a valgrind bug.

-- 
Hanno Böck
https://hboeck.de/

mail/jabber: hanno@hboeck.de
GPG: FE73757FA60E4E21B937579FA5880072BBB51E42