This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: valgrind confused by std::allocator calls to operator new(0)

From: Benjamin Kosnik <bkoz at redhat dot com>
To: Paolo Carlini <pcarlini at suse dot de>
Cc: Michael Veksler <VEKSLER at il dot ibm dot com>, libstdc++ at gcc dot gnu dot org
Date: Tue, 22 Feb 2005 10:57:24 -0600
Subject: Re: valgrind confused by std::allocator calls to operator new(0)
Organization: Red Hat / Chicago
References: <OF63B462D7.F58248F0-ON42256FB0.001F86A2-42256FB0.0024499E@il.ibm.com><421B011B.8020403@suse.de>

> I agree that calling new(0) is dumb and we should simply standardize on 
> the behavior of pool and mt: it's just a matter of adding a conditional 
> to new_allocator, seems safe for 3.4.4 too. Please file a PR, thanks.

Agreed. I'll fix this up.

-benjamin

References:
- valgrind confused by std::allocator calls to operator new(0)
  - From: Michael Veksler
- Re: valgrind confused by std::allocator calls to operator new(0)
  - From: Paolo Carlini

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]