|Subject:||Re: Running bash under valgrind gives "invalid free()"|
|Date:||Thu, 13 Apr 2017 09:15:55 +0100|
On Wed, 12 Apr 2017 14:59:26 +0100
Reuben Thomas <address@hidden> 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.
|[Prev in Thread]||Current Thread||[Next in Thread]|