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

[Reuben Thomas]

On 13 April 2017 at 21:17, Chet Ramey <chet.ramey@case.edu> wrote:

On 4/13/17 3:57 PM, Reuben Thomas wrote:

> Meanwhile, in the valgrind bug report, Mark Wielaard observed:
>
> "I think the problem is that bash not only has its own malloc/free
> implementation (valgrind should intercept that just fine). But also has
> malloc wrappers for some malloc functions that call their internal
> counterparts directly (so valgrind won't know that is a matching
> allocation/deallocation function)."

Yes, if he wants the details, feel free to forward my message from earlier
today.

​Thanks, I

​ already linked to it in the valgrind bug report

.​

​​

--

http://rrt.sc3d.org