From: Markus.Grunwald@pruftechnik.com
To: gdb@sourceware.org
Subject: faster printing of QStrings
Date: Thu, 22 Mar 2007 12:30:00 -0000 [thread overview]
Message-ID: <OFF8FB08FC.7E6D07C5-ONC12572A6.004381A6-C12572A6.00448247@pruftechnik.com> (raw)
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:
define pqs
set $i=0
set $unicode=$arg0.d->unicode
printf "Getting QString...\n"
while $i < $arg0.d->len
set $c=$unicode[$i++].ucs
if $c < 32
printf "\\0%o", $c
else
if $c <= 127
printf "%c", $c
else
printf "\\0%o", $c
end
end
end
echo \n
end
(gdb) pqs oszPrinterLine
Getting QString...
kopierer akzeptiert Anfragen seit Mo 19 Feb 2007 13:27:28 CET
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... ?
Mit freundlichen Grüßen
Markus Grunwald
Softwareentwicklung
PRÜFTECHNIK Condition Monitoring GmbH
Oskar-Messter-Straße 19-21
85737 Ismaning
www.pruftechnik.com
Tel: +49 (0)89 99616177
Fax: +49 (0)89 99616200
PRÜFTECHNIK Condition Monitoring GmbH
Sitz Ismaning / HRB 145655 München
Geschäftsführer: Johann Lösl, Roland Schühle
Ein Unternehmen der PRÜFTECHNIK-Gruppe
next reply other threads:[~2007-03-22 12:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 12:30 Markus.Grunwald [this message]
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
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=OFF8FB08FC.7E6D07C5-ONC12572A6.004381A6-C12572A6.00448247@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