This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Slow handling of C++ symbol names

From: Andrew Cagney <ac131313 at redhat dot com>
To: Daniel Jacobowitz <drow at mvista dot com>
Cc: Will Cohen <wcohen at redhat dot com>, gdb at sources dot redhat dot com
Date: Thu, 20 Nov 2003 11:08:59 -0500
Subject: Re: Slow handling of C++ symbol names
References: <3FBBDC27.50204@redhat.com> <20031119211355.GA31069@nevyn.them.org>


Have you tried a more recent version of GDB?  This may have been
improved.  Definitely some startup time issues were fixed.

Nothing in the ChangeLogs jumped out.

Also, the demangler actually comes from GCC, not GDB.

I don't see GCC being motivated to fix it though :-(

>  All we can do is
> try to call it less often.

Which leads to the question. Why does GDB demangle symbols? My simplistic understanding of the code is that GDB only needs the "iw" (a.k.a., demangled string up to but excluding the lparen and ignoring white space) part of the symbol in the search table (the rest isn't so critical and can be constructed on-demand).

Andrew

Follow-Ups:
- Re: Slow handling of C++ symbol names
  - From: Daniel Jacobowitz

References:
- Re: Slow handling of C++ symbol names
  - From: Daniel Jacobowitz

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]