This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: valgrind confused by std::allocator calls to operator new(0)
- From: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- To: Michael Veksler <VEKSLER at il dot ibm dot com>
- Cc: libstdc++ at gcc dot gnu dot org
- Date: 22 Feb 2005 14:40:04 +0100
- Subject: Re: valgrind confused by std::allocator calls to operator new(0)
- Organization: Integrable Solutions
- References: <OF63B462D7.F58248F0-ON42256FB0.001F86A2-42256FB0.0024499E@il.ibm.com>
Michael Veksler <VEKSLER@il.ibm.com> writes:
| Is it possible/reasonable to change new_allocator::allocate such that
| it returns NULL when __n ==0 ? Should I open a PR against libstdc++?
Yes, please.
-- Gaby