From: Ian Lance Taylor <ian@wasabisystems.com>
To: David Carlton <carlton@kealia.com>
Cc: gdb <gdb@sources.redhat.com>
Subject: Re: new demangler
Date: Mon, 15 Dec 2003 23:10:00 -0000 [thread overview]
Message-ID: <m3y8tdfzir.fsf@gossamer.airs.com> (raw)
In-Reply-To: <yf2he01vg6z.fsf@hawaii.kealia.com>
David Carlton <carlton@kealia.com> writes:
> Hmm. I don't have a CVS binutils tree around, but I get, with GDB
> from current CVS:
>
> (gdb) maint demangle _ZN1C6CClassaSERKS0_
> Can't demangle "_ZN1C6CClassaSERKS0_"
>
> So either we're using different demanglers or else there's something
> strange about maint demangle/class_name_from_physname. Either of
> which is possible - nobody other than me uses class_name_from_physname
> regularly, after all, and maint demangle is only a maint command.
`maint demangle' only works for me when I explicitly run gdb on a C++
program. When I do specify a C++ program, it appears to work
correctly.
Otherwise, I see that maintenance_demangle() calls
language_demangle(). When I try running gdb without an explicit C++
program, either current_language is NULL or
current_language->la_demangle is NULL, so language_demangle returns
NULL.
Ian
next prev parent reply other threads:[~2003-12-15 23:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-15 22:53 David Carlton
2003-12-15 22:54 ` Daniel Jacobowitz
2003-12-15 23:01 ` David Carlton
2003-12-15 23:10 ` Ian Lance Taylor [this message]
2003-12-15 23:17 ` David Carlton
2003-12-15 23:20 ` Ian Lance Taylor
2003-12-15 23:23 ` Ian Lance Taylor
2003-12-15 23:29 ` David Carlton
2003-12-15 23:33 ` Ian Lance Taylor
2003-12-15 23:38 ` David Carlton
2003-12-16 5:30 ` Daniel Jacobowitz
2003-12-18 2:22 ` Jim Blandy
2003-12-18 2:58 ` Ian Lance Taylor
2003-12-18 5:21 ` Daniel Jacobowitz
2003-12-18 16:01 ` Ian Lance Taylor
2003-12-15 23:16 Michael Elizabeth Chastain
2003-12-15 23:55 Michael Elizabeth Chastain
2003-12-18 4:04 Michael Elizabeth Chastain
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=m3y8tdfzir.fsf@gossamer.airs.com \
--to=ian@wasabisystems.com \
--cc=carlton@kealia.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