From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10207 invoked by alias); 22 Sep 2006 14:40:49 -0000 Received: (qmail 10102 invoked by uid 48); 22 Sep 2006 14:40:39 -0000 Date: Fri, 22 Sep 2006 14:40:00 -0000 Message-ID: <20060922144039.10101.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug libstdc++/29179] bugs in mt_allocator In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "random at adriver dot ru" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2006-09/txt/msg02146.txt.bz2 List-Id: ------- Comment #4 from random at adriver dot ru 2006-09-22 14:40 ------- (In reply to comment #3) > No, for the simple reason that the allocator does not work is __block_count > turns out to be zero. The problem with your PR is that you are doing sort of > syntactical analysis of the code without understandind the functioning of the > allocator. ok, perhaps this is not really a bug, however segfault is not very user friendly. could ASSERT solve it? about the first one, I take it you agree that it is a real bug? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29179