From: Tom Tromey <tromey@redhat.com>
To: Project Archer <archer@sourceware.org>
Subject: dwarf name canonicalization
Date: Tue, 23 Feb 2010 20:52:00 -0000 [thread overview]
Message-ID: <m3zl2zy8sa.fsf@fleche.redhat.com> (raw)
Keith, do you happen to know offhand what things in gdb rely on
canonicalizing C++ names in the dwarf reader?
I was discussing this canonicalization with a user who prefers to remain
anonymous. His experience is that this canonicalization greatly slows
down gdb startup (he said 15%), and in his experience isn't needed for
his use case, which is running gdb as part of an IDE.
I'm wondering whether it would make sense to somehow disable this, maybe
via some special mode for IDEs to use. I thought maybe you'd know what
would break...
My understanding is that the typical IDE use cases are much more
restricted than what CLI users do. E.g., in the IDE case, most
breakpoints are set by "file:line" and expression evaluation is not as
important.
Tom
next reply other threads:[~2010-02-23 20:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 20:52 Tom Tromey [this message]
2010-02-23 22:07 ` Keith Seitz
2010-02-25 11:16 ` André Pönitz
2010-02-25 19:38 ` Tom Tromey
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=m3zl2zy8sa.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=archer@sourceware.org \
/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).