This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC 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: segfault with std::allocator

From: Toon Knapen <toon dot knapen at fft dot be>
To: Eljay Love-Jensen <eljay at adobe dot com>
Cc: gcc-help at gcc dot gnu dot org
Date: Fri, 03 Sep 2004 15:57:04 +0200
Subject: Re: segfault with std::allocator
References: <41387052.1090406@fft.be> <6.1.2.0.2.20040903084315.01f8aea8@iplan-mn.corp.adobe.com>

Eljay Love-Jensen wrote:

Hi Toon,

The deallocate function MUST NOT by passed in a NULL pointer. (According to ISO 14882.)

But 20.4.1.1 par 8 only says "p shall be a pointer obtained from allocate(). n shall equal the value passed as the first argument to the invocation of allocate which returned p". Next as a not is added that it uses '::operator delete' and delete is allowed to be called on a NULL pointer.

Follow-Ups:
- Re: segfault with std::allocator
  - From: Eljay Love-Jensen

References:
- segfault with std::allocator
  - From: Toon Knapen
- Re: segfault with std::allocator
  - From: Eljay Love-Jensen

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