From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-32716-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 20599 invoked by alias); 5 Aug 2008 12:56:26 -0000
Received: (qmail 20466 invoked by uid 22791); 5 Aug 2008 12:56:25 -0000
X-Spam-Check-By: sourceware.org
Received: from hoat.troll.no (HELO hoat.troll.no) (62.70.27.150)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 05 Aug 2008 12:55:41 +0000
Received: from hoat.troll.no (tedur.troll.no [62.70.27.154]) 	by hoat.troll.no (Postfix) with SMTP id 99CF620754 	for <gdb@sources.redhat.com>; Tue,  5 Aug 2008 14:55:38 +0200 (CEST)
Received: from gar.trolltech.de (gar.trolltech.de [10.4.0.24]) 	by hoat.troll.no (Postfix) with ESMTP id 844072074D 	for <gdb@sources.redhat.com>; Tue,  5 Aug 2008 14:55:38 +0200 (CEST)
From: =?iso-8859-1?q?Andr=E9_P=F6nitz?= <apoenitz@trolltech.com>
To: gdb@sources.redhat.com
Subject: Re: gdb problem with  'malloc' in unnamed namespace
Date: Tue, 05 Aug 2008 12:56:00 -0000
User-Agent: KMail/1.9.9
References: <200808051407.14091.apoenitz@trolltech.com> <je63qfws8e.fsf@sykes.suse.de>
In-Reply-To: <je63qfws8e.fsf@sykes.suse.de>
MIME-Version: 1.0
Content-Type: text/plain;   charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200808051458.24031.apoenitz@trolltech.com>
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2008-08/txt/msg00069.txt.bz2

On Tuesday 05 August 2008 14:39:45 you wrote:
> Andr=E9 P=F6nitz <apoenitz@trolltech.com> writes:
>=20
> > So the 'malloc' from the debugged program is picked up by gdb, even if =
the
> > symbol name ("_ZN29_GLOBAL__N__00000000_271D34D06mallocEv") does
> > not match.
>=20
> Note that symbol lookup also considers the demangled name, which matches
> here.

Well, "demangled" in a very C-ish sense: drop all namespace and parameter
information. The symbol name contains parameter information that might
be useful to determine that this is not a suitable kind of malloc:

...$ c++filt=20
_ZN29_GLOBAL__N__00000000_271D34D06mallocEii
(anonymous namespace)::malloc(int, int)

Anyway, thanks for the great hint!

Regards,
Andr=E9