From: "Dima S" <spiridenok@tut.by>
To: Paul Koning <pkoning@equallogic.com>
Cc: gdb@sourceware.org
Subject: Re: C++ names in backtrace
Date: Fri, 07 Dec 2007 08:29:00 -0000 [thread overview]
Message-ID: <web-448141089@speedy.tutby.com> (raw)
In-Reply-To: <18262.48200.586110.349260@pkoning-laptop.equallogic.com>
I've downloaded & built a version of c++filt (version GNU c++filt (GNU
Binutils)2.18 to be more precise).
When i run the c++filt program with my mangles names i get correct demangled
names on the output:
Examples (the mandgled names used here can be found in my previous posts):
./binutils/cxxfilt _ZN7WSLCLAG21select_actuator_parmsEi
WSLCLAG::select_actuator_parms(int)
./binutils/cxxfilt _ZN7CxxTest14ErrorFormatter3runEv
CxxTest::ErrorFormatter::run()
./binutils/cxxfilt _ZN7WSLCLAG7destroyEv
WSLCLAG::destroy()
So it seems that i can demangle the names from gdb backtrace using c++filt.
Does it mean/say anything to anybody?
How can i get demangled names in gdb?
Thanks in advance!
Wed, 5 Dec 2007 09:57:12 -0500, Paul Koning <pkoning@equallogic.com>:
>
>>>>>> "Dima" == Dima S <spiridenok@tut.by> writes:
>
> Dima> Sorry but i'm not familiar with "c++filt"... What is it and
> Dima> how can i feed my mangled names to it?
>
> It's one of the GNU tools, like gcc. You'll find it in the same
> place.
>
>Feed it the names you want to demangle to its stdin, and they will
> come out to stdout.
>
> paul
>
-----------
WWW.PIZZA.BY - Äîñòà âêà Гà äîì èëè Гў îôèñ ïèööû, Г±ГіГёГЁ, øà øëûêà ,
Гà ïèòêîâ êðóãëîñóòî÷ГГ®. http://pizza.by
next prev parent reply other threads:[~2007-12-07 8:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 10:38 Bobo
2007-11-30 14:46 ` Daniel Jacobowitz
2007-11-30 14:52 ` Paul Koning
2007-11-30 15:03 ` Dima S
2007-11-30 18:45 ` Stan Shebs
2007-12-05 12:49 ` Dima S
[not found] ` <18262.48200.586110.349260@pkoning-laptop.equallogic.com>
2007-12-07 8:29 ` Dima S [this message]
[not found] ` <18256.10018.785226.339384@pkoning-laptop.equallogic.com>
2007-12-05 12:47 ` Dima S
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=web-448141089@speedy.tutby.com \
--to=spiridenok@tut.by \
--cc=gdb@sourceware.org \
--cc=pkoning@equallogic.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).