From: "André Pönitz" <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 [thread overview]
Message-ID: <200808051458.24031.apoenitz@trolltech.com> (raw)
In-Reply-To: <je63qfws8e.fsf@sykes.suse.de>
On Tuesday 05 August 2008 14:39:45 you wrote:
> André Pönitz <apoenitz@trolltech.com> writes:
>
> > 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.
>
> 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
_ZN29_GLOBAL__N__00000000_271D34D06mallocEii
(anonymous namespace)::malloc(int, int)
Anyway, thanks for the great hint!
Regards,
André
prev parent reply other threads:[~2008-08-05 12:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 12:05 André Pönitz
2008-08-05 12:13 ` Daniel Jacobowitz
2008-08-05 12:40 ` Andreas Schwab
2008-08-05 12:56 ` André Pönitz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200808051458.24031.apoenitz@trolltech.com \
--to=apoenitz@trolltech.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox