Re: [Valgrind-users] Re: Recommended gcc version

[Nicholas N. <nj...@ca...>]

On Tue, 10 Jun 2003, Melchior FRANZ wrote:

> I can confirm that cvs/head gives hundreds of bogus error messages
> about mismatched allocation. I only checked one of them and saw that
> the concerned code creates an automatic variable of a c++ object.
> valgrind obviously complains when the auto var is to be destroyed
> at function end. The bug was introduced with "vg_replace_malloc.c"
> revision 1.7. (1.6 did still work.)

We've rolled back to 1.6 in CVS.  The change was intended to fix another
problem, but ended up breaking more things than it fixed, on some
machines.  Thanks for the feedback.

N