From: "Paweł Sikora" <pawel.sikora@agmk.net>
To: gdb@sourceware.org
Subject: very slow gdb stepping.
Date: Sat, 31 Mar 2012 13:05:00 -0000 [thread overview]
Message-ID: <1809128.jWeFzAnxpv@localhost> (raw)
Hi all,
during debugging a large c++ application an each gdb step (next or step-in)
takes from ~2 to ~30 seconds which is horribly slow and uncomfortable :(
the callgrind shows some hot places in gdb: http://carme.pld-linux.org/~pluto/gdb-cpuhog/callgraph.png
callgrind results from ~30min session and .rpms are stored here:
http://carme.pld-linux.org/~pluto/gdb-cpuhog/
is it a known issue?
next reply other threads:[~2012-03-31 13:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-31 13:05 Paweł Sikora [this message]
2012-03-31 21:57 ` Jan Kratochvil
2012-03-31 22:01 ` Jan Kratochvil
2012-04-01 9:19 ` Paweł Sikora
2012-04-01 10:44 ` Paweł Sikora
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=1809128.jWeFzAnxpv@localhost \
--to=pawel.sikora@agmk.net \
--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