From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18832 invoked by alias); 11 Sep 2009 20:09:11 -0000 Received: (qmail 18795 invoked by uid 48); 11 Sep 2009 20:08:59 -0000 Date: Fri, 11 Sep 2009 20:09:00 -0000 From: "kees at outflux dot net" To: glibc-bugs@sources.redhat.com Message-ID: <20090911200859.10631.kees@outflux.net> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug libc/10631] New: clarify malloc error message to avoid confusion X-Bugzilla-Reason: CC Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org X-SW-Source: 2009-09/txt/msg00023.txt.bz2 The current malloc error message template is "*** glibc detected *** [argv0]: [error]: [addr] ***". Due to the second "***", the whole message is frequently parsed as two statements, leading to confusion for some people. The phrase "glibc detected" is misleading, since it was not glibc that was detected but rather the error itself. glibc did the detecting. ("[I have] detected glibc" vs "glibc detected [an error]".) I would suggest one of: - dropping the middle ***'s - changing the "glibc detected" string to "malloc error" - dropping the middle ***'s and changing the "glibc detected" string to "glibc has detected" -- Summary: clarify malloc error message to avoid confusion Product: glibc Version: 2.11 Status: NEW Severity: normal Priority: P2 Component: libc AssignedTo: drepper at redhat dot com ReportedBy: kees at outflux dot net CC: glibc-bugs at sources dot redhat dot com http://sourceware.org/bugzilla/show_bug.cgi?id=10631 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.