From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Make target_read_string faster over high-latency links.
Date: Tue, 26 Jul 2011 11:15:00 -0000 [thread overview]
Message-ID: <20110726083612.GA32633@host1.jankratochvil.net> (raw)
In-Reply-To: <20110715180748.A0390190BC2@elbrus2.mtv.corp.google.com>
On Fri, 15 Jul 2011 20:07:48 +0200, Paul Pluzhnikov wrote:
> This is GDB walking through the shared library list, and reading shared
> library names from gdbserver via target_read_string 4 bytes at a time ;-(
Just that you do not mention supporting qXfer:libraries:read also on GNU/Linux
platforms (currently used only on MS-Windows), that is to move solib-svr4.c to
gdb/common/ etc.
It is sure a larger change but it could bring even a better performance.
Thanks,
Jan
prev parent reply other threads:[~2011-07-26 8:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 18:09 Paul Pluzhnikov
2011-07-18 18:06 ` Tom Tromey
2011-07-18 19:01 ` Paul Pluzhnikov
2011-07-19 17:44 ` Paul Pluzhnikov
2011-07-19 17:52 ` Tom Tromey
2011-07-22 16:53 ` Joel Brobecker
2011-07-22 17:01 ` Paul Pluzhnikov
2011-07-25 14:42 ` Daniel Jacobowitz
2011-07-26 11:15 ` Jan Kratochvil [this message]
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=20110726083612.GA32633@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=ppluzhnikov@google.com \
/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