public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jens dot elmenthaler at verigy dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/11555] 100% CPU for minutes trying to print expresion
Date: Fri, 30 Apr 2010 13:51:00 -0000 [thread overview]
Message-ID: <20100430135059.944.qmail@sourceware.org> (raw)
In-Reply-To: <20100428195619.11555.jlquinn@us.ibm.com>
------- Additional Comments From jens dot elmenthaler at verigy dot com 2010-04-30 13:50 -------
(In reply to comment #1)
> This might be the same issue as:
> http://sourceware.org/bugzilla/show_bug.cgi?id=11408
> could you try with this patch:
> http://sourceware.org/bugzilla/attachment.cgi?id=4674&action=view
bug11408 should already be fixed if I check out the latest gdb sources from
7.1 branch, right (done today)? At least I found a ChangeLog saying this.
The sluggishness while stepping seems to be gone, but inserting a break point
is still damn slow.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=11555
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2010-04-30 13:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 19:56 [Bug gdb/11555] New: " jlquinn at us dot ibm dot com
2010-04-28 20:07 ` [Bug gdb/11555] " swagiaal at redhat dot com
2010-04-29 15:14 ` swagiaal at redhat dot com
2010-04-30 9:13 ` jens dot elmenthaler at verigy dot com
2010-04-30 13:51 ` jens dot elmenthaler at verigy dot com [this message]
2010-04-30 14:27 ` swagiaal at redhat dot com
2010-04-30 14:38 ` jens dot elmenthaler at verigy dot com
2010-04-30 15:46 ` jlquinn at us dot ibm dot com
2010-04-30 18:04 ` tromey at redhat dot com
2010-04-30 18:26 ` jens dot elmenthaler at verigy dot com
2010-05-04 14:24 ` swagiaal at redhat dot com
[not found] <bug-11555-4717@http.sourceware.org/bugzilla/>
2022-10-21 17:03 ` tromey at sourceware dot org
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=20100430135059.944.qmail@sourceware.org \
--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).