Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@wasabisystems.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Michael Elizabeth Chastain <mec.gnu@mindspring.com>,
	ac131313@redhat.com, gdb@sources.redhat.com, wcohen@redhat.com
Subject: Re: Slow handling of C++ symbol names
Date: Wed, 03 Dec 2003 17:54:00 -0000	[thread overview]
Message-ID: <m365gxeqj2.fsf@gossamer.airs.com> (raw)
In-Reply-To: <20031203173755.GA4506@nevyn.them.org>

Daniel Jacobowitz <drow@mvista.com> writes:

> On Wed, Dec 03, 2003 at 12:34:31PM -0500, Ian Lance Taylor wrote:
> > Daniel Jacobowitz <drow@mvista.com> writes:
> > 
> > > GDB never does set DMGL_VERBOSE.  Are you sure the old demangler
> > > wouldn't produce that without DMGL_VERBOSE?
> > > 
> > > Maybe the old demangler had a test reversed.  ISTR that c++filt passes
> > > DMGL_VERBOSE, and that generates std::string rather than
> > > std::basic_string for the above.
> > 
> > Well, hmmm.  The code looks right to me.  When I run my copy of
> > c++filt built with the old demangler, I get the long string, as
> > expected.
> > 
> > I note that DMGL_VERBOSE was only added on 2002-02-05, so if you're
> > using a c++filt from sources before that you will get the smaller
> > demangling.
> 
> I'm using one from binutils as of a month or so ago, and I get the
> short string.  Hmm.  I don't know quite what's going on.

Me neither.

Everything makes sense to me and I get the results I expect.  If we
want to pursue this further, though it may not matter much, I think
you need to debug your c++filt.  See if flag_verbose is set.  The
relevant function is called demangle_substitution().  The first call
to the function will call result_add() with either std::string or the
longer version.

Ian


  reply	other threads:[~2003-12-03 17:54 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-03 16:48 Michael Elizabeth Chastain
2003-12-03 16:52 ` David Carlton
2003-12-03 16:58 ` Ian Lance Taylor
2003-12-03 17:08   ` Daniel Jacobowitz
2003-12-03 17:34     ` Ian Lance Taylor
2003-12-03 17:38       ` Daniel Jacobowitz
2003-12-03 17:54         ` Ian Lance Taylor [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-12-03 22:30 Michael Elizabeth Chastain
2003-12-03 20:27 Michael Elizabeth Chastain
2003-12-03 20:35 ` Ian Lance Taylor
2003-12-03 20:17 Michael Elizabeth Chastain
2003-12-03 20:14 Michael Elizabeth Chastain
2003-12-03 19:57 Michael Elizabeth Chastain
2003-12-03 20:16 ` Daniel Jacobowitz
2003-12-02 22:38 Michael Elizabeth Chastain
2003-12-02 22:09 Michael Elizabeth Chastain
2003-12-02 22:23 ` Ian Lance Taylor
2003-12-02 22:29   ` Daniel Jacobowitz
2003-12-03 18:52 ` Andrew Cagney
     [not found] <3FBBDC27.50204@redhat.com>
2003-11-19 21:13 ` Daniel Jacobowitz
2003-11-20 16:09   ` Andrew Cagney
2003-11-20 16:19     ` Daniel Jacobowitz
2003-11-20 16:54       ` Andrew Cagney
2003-11-20 16:58         ` Daniel Jacobowitz
2003-11-21 17:58         ` Daniel Jacobowitz
2003-11-26 14:27           ` Andrew Cagney
2003-11-26 16:24             ` Will Cohen
2003-11-26 20:48               ` Andrew Cagney
2003-11-26 20:45             ` Will Cohen

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=m365gxeqj2.fsf@gossamer.airs.com \
    --to=ian@wasabisystems.com \
    --cc=ac131313@redhat.com \
    --cc=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    --cc=mec.gnu@mindspring.com \
    --cc=wcohen@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