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

bug-bash

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From:	Reuben Thomas
Subject:	Re: Running bash under valgrind gives "invalid free()"
Date:	Thu, 13 Apr 2017 11:32:45 +0100

On 13 April 2017 at 09:15, Reuben Thomas <rrt@sc3d.org> wrote:

Having confirmed Chet's analysis with a few printfs added to bash (i.e. just to check the address being allocated and the one complained about were the same) I've filed a bug report against valgrind: https://bugs.kde.org/show_bug.cgi?id=378732

Julian Seward (valgrind author) correctly

guessed that it is a problem with malloc/free interception: when bash uses its own malloc (as by default on my GNU/Linux system), the malloc is not intercepted by valgrind, but the free is.

Obviously a bug in valgrind, but I am interested: why does bash not use the glibc malloc by default on GNU/Linux systems?

http://rrt.sc3d.org

[Prev in Thread]

Current Thread

[Next in Thread]

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

Prev by Date: Re: Running bash under valgrind gives "invalid free()"
Next by Date: Re: Running bash under valgrind gives "invalid free()"
Previous by thread: Re: Running bash under valgrind gives "invalid free()"
Next by thread: Re: Running bash under valgrind gives "invalid free()"
Index(es):
- Date
- Thread