Re: Running bash under valgrind gives "invalid free()"
From:
Chet Ramey
Subject:
Re: Running bash under valgrind gives "invalid free()"
Date:
Thu, 13 Apr 2017 10:11:19 -0400
User-agent:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
On 4/13/17 6:32 AM, Reuben Thomas wrote:
> Obviously a bug in valgrind, but I am interested: why does bash not use the
> glibc malloc by default on GNU/Linux systems?
The bash malloc is faster; better tuned for bash; is more signal safe
without the twisty maze of locks that the glibc malloc uses; and includes
things like bounds checking and duplicate free detection by default.
--
``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/