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

[Chet Ramey]

On 4/12/17 12:58 PM, Hanno Böck wrote:
> 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.

It's a valgrind false positive. I run the entire bash test suite through
a version built with address sanitizer.

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://cnswww.cns.cwru.edu/~chet/