From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5041 invoked by alias); 21 May 2009 09:15:37 -0000 Received: (qmail 4930 invoked by uid 48); 21 May 2009 09:15:25 -0000 Date: Thu, 21 May 2009 09:15:00 -0000 Message-ID: <20090521091525.4929.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug libstdc++/40094] FAIL: ext/throw_allocator/deallocate_global.cc execution test In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "paolo dot carlini at oracle dot com" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2009-05/txt/msg01762.txt.bz2 ------- Comment #5 from paolo dot carlini at oracle dot com 2009-05-21 09:15 ------- So, you should compare it to the previous delete, which normally should be the *only* one involving basic_string. To be clear, the expected sequence is the following, as you can check on any other linux target: operator new is called operator new is called operator delete is called 1 allocations to be released operator delete is called All memory released that is, the additional delete / new pair that you are seeing at the end is completely bogus. Of course, I would suggest also checking what happens vs optimization level (also for the *.so, thus rebuilding the library CXXFLAGS="-OX -g"). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40094