public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tobias.hunger at digia dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/15412] Performance regression in "info {func,var,types} foo" (mostly info types).
Date: Fri, 17 May 2013 10:09:00 -0000 [thread overview]
Message-ID: <bug-15412-4717-9DrgiMRC4I@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15412-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=15412
Tobias Hunger <tobias.hunger at digia dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tobias.hunger at digia dot
| |com
--- Comment #1 from Tobias Hunger <tobias.hunger at digia dot com> 2013-05-17 10:09:22 UTC ---
I see the same issue debugging C++ applications using GDB 7.6 with Qt Creator.
Getting a list of local variables and their values after hitting a breakpoint
takes at least 10s where it is almost instantaneous in GDB 7.5.
This time can increase dramatically (> 2 min!) with the complexity of the code
containing the breakpoint.
GDB 7.6 is not usable in this setup, I had to revert back to GDB 7.5. I would
seriously consider raising the importance of this regression.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-05-17 10:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-27 21:34 [Bug symtab/15412] New: " dje at google dot com
2013-05-17 10:09 ` tobias.hunger at digia dot com [this message]
2013-05-19 13:50 ` [Bug symtab/15412] " xunxun1982 at gmail dot com
2013-05-24 13:49 ` asmwarrior at gmail dot com
2013-05-24 14:33 ` asmwarrior at gmail dot com
2013-05-29 12:23 ` andre.poenitz at digia dot com
2013-06-05 4:52 ` flq at live dot com
2014-01-25 21:02 ` altsysrq at gmail dot com
2014-06-16 1:39 ` asmwarrior at gmail dot com
2015-02-21 14:27 ` dje at google dot com
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=bug-15412-4717-9DrgiMRC4I@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).