From: Antonio Cavallo <a.cavallo@cavallinux.eu>
To: gdb@sourceware.org
Subject: gdb symbol lookup very slow
Date: Wed, 28 May 2014 08:56:00 -0000 [thread overview]
Message-ID: <53859746.7030601@cavallinux.eu> (raw)
Hi,
I'm having hard time debugging a (very large) C++ library under gdb (gdb
7.7.1, gcc 4.8, binutils 2.22).
The main issue is the time it takes to reach a breakpoint: gdb takes an
insane amount of time (order of 2mins) vs vs2012 (a couple of seconds).
I've profiled gdb and the top functions called during the debugging are
(more than 90% is spent in these):
strcmp_iw
find_pc_sect_psymtab
symbol_get_demangled_name
symbol_search_name
I suspect gdb doesn't cache the symbols: is there any way to speedup
this lookup? Is there any other explanation for why gdb is so much
slower than visual studio?
I've repeated the run with lldb (from svn), and it is at least two times
faster than gdb.
Any suggestion where to look for?
Thanks
next reply other threads:[~2014-05-28 7:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 8:56 Antonio Cavallo [this message]
2014-05-28 22:43 ` Andrew Burgess
2014-05-29 2:48 ` Antonio Cavallo
2014-05-29 20:40 ` Jan Kratochvil
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=53859746.7030601@cavallinux.eu \
--to=a.cavallo@cavallinux.eu \
--cc=gdb@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