Re: segfault with std::allocator

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

To: Toon Knapen <toon.knapen@xxxxxx>
Subject: Re: segfault with std::allocator
From: Eljay Love-Jensen <eljay@xxxxxxxxx>
Date: Fri, 03 Sep 2004 09:33:54 -0500
Cc: gcc-help@xxxxxxxxxxx
In-reply-to: <41387830.8020709@fft.be>
References: <41387052.1090406@fft.be> <6.1.2.0.2.20040903084315.01f8aea8@iplan-mn.corp.adobe.com> <41387830.8020709@fft.be>
Sender: gcc-help-owner@xxxxxxxxxxx

Hi Toon,

You're not calling delete, your calling int_alloc.deallocate(p, 0);

And the deallocate routine (in ISO 14882, table 32 in 20.1.5) specifically says "p must not be null".

--Eljay

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

Prev by Date: Re: segfault with std::allocator
Next by Date: Building on an AIX Bare Minimum System
Previous by thread: Re: segfault with std::allocator
Next by thread: Building on an AIX Bare Minimum System
Index(es):
- Date
- Thread

[Index of Archives] [Linux C Programming] [Linux Kernel] [eCos] [Fedora Development] [Fedora Announce] [Autoconf] [The DWARVES Debugging Tools] [Yosemite Campsites] [Yosemite News] [Linux GCC]

Powered by Linux