From: Markus.Grunwald@pruftechnik.com
To: gdb@sourceware.org
Subject: Re: faster printing of QStrings
Date: Thu, 22 Mar 2007 15:19:00 -0000 [thread overview]
Message-ID: <OFDBB6371B.5D0A9519-ONC12572A6.0054290A-C12572A6.00543007@pruftechnik.com> (raw)
Hello,
> Thanks for posting this - I'm sure it will be useful to someone, and
> it's also a good test case for GDB performance :-)
:)
> I couldn't think of anything. It's probably the array access and a
> pile of symbol lookups that are slowing it down; when I can find time
> (no promises, but this was already on top of my todo list) I will try
> to speed it up.
Perhaps a look into the kdevelop code could help - they do it somehow ...
> The only way you could use it with display today is by defining a
> hook-stop macro.
I'll have a look how this works.
Thanks !
Markus
next reply other threads:[~2007-03-22 15:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 15:19 Markus.Grunwald [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-22 12:30 Markus.Grunwald
2007-03-22 12:42 ` Daniel Jacobowitz
2007-03-23 13:08 ` Eli Zaretskii
2007-03-22 13:50 ` Ramana Radhakrishnan
2007-03-22 15:03 ` Markus.Grunwald
2007-03-23 13:10 ` Eli Zaretskii
2007-03-23 14:00 ` Markus.Grunwald
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=OFDBB6371B.5D0A9519-ONC12572A6.0054290A-C12572A6.00543007@pruftechnik.com \
--to=markus.grunwald@pruftechnik.com \
--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