From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16236 invoked by alias); 6 Nov 2006 20:35:48 -0000 Received: (qmail 16200 invoked by uid 48); 6 Nov 2006 20:35:39 -0000 Date: Mon, 06 Nov 2006 20:35:00 -0000 Message-ID: <20061106203539.16199.qmail@sourceware.org> From: "drepper at redhat dot com" To: glibc-bugs@sources.redhat.com In-Reply-To: <20061106201514.3462.jrweave@gmail.com> References: <20061106201514.3462.jrweave@gmail.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug libc/3462] Malloc memory corruption when malloc(...) called X-Bugzilla-Reason: CC Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org X-SW-Source: 2006-11/txt/msg00017.txt.bz2 List-Id: ------- Additional Comments From drepper at redhat dot com 2006-11-06 20:35 ------- The message clearly says that glibc *detected* the problem. Not caused it. Your program is corrupting memory somewhere somehow and glibc finally notices it. Use valgrind or mudflap or similar tools to detect your mistake. -- What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID http://sourceware.org/bugzilla/show_bug.cgi?id=3462 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.