Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Markus.Grunwald@pruftechnik.com
Cc: gdb@sourceware.org
Subject: Re: faster printing of QStrings
Date: Thu, 22 Mar 2007 12:42:00 -0000	[thread overview]
Message-ID: <20070322123906.GA30375@caradoc.them.org> (raw)
In-Reply-To: <OFF8FB08FC.7E6D07C5-ONC12572A6.004381A6-C12572A6.00448247@pruftechnik.com>

On Thu, Mar 22, 2007 at 01:28:18PM +0100, Markus.Grunwald@pruftechnik.com wrote:
> Hello,
> 
> we are developing Qt applications. kdevelops debugger offers a watch where 
> it can display QStrings. I am more the commandline user and have found a 
> nice function that prints QStrings with gdb:

Thanks for posting this - I'm sure it will be useful to someone, and
it's also a good test case for GDB performance :-)

> Works fine - except that it takes ages (25s) ! Kdevelop displays the 
> QStrings in an instant. Now I wonder if there is a faster way of getting 
> this information in gdb - and maybe even to "display oszPrinterLine" which 
> makes sense only if printing is fast... ?

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.

The only way you could use it with display today is by defining a
hook-stop macro.  I would like to offer something better involving
integrated Python, but it probably won't happen until next year.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-03-22 12:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-22 12:30 Markus.Grunwald
2007-03-22 12:42 ` Daniel Jacobowitz [this message]
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
2007-03-22 15:19 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=20070322123906.GA30375@caradoc.them.org \
    --to=drow@false.org \
    --cc=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