From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Make target_read_string faster over high-latency links.
Date: Tue, 19 Jul 2011 17:44:00 -0000 [thread overview]
Message-ID: <CALoOobM_+CJi3fWNk7C0K2ApRS76uRo9r6scDYCQnJHf8VSkBg@mail.gmail.com> (raw)
In-Reply-To: <CALoOobMZEbQDQOWM4iPOP9ORm5DLDaLoqZXO5YYHaf+hV+DS6g@mail.gmail.com>
On Mon, Jul 18, 2011 at 11:06 AM, Paul Pluzhnikov
<ppluzhnikov@google.com> wrote:
> On Mon, Jul 18, 2011 at 10:09 AM, Tom Tromey <tromey@redhat.com> wrote:
>
> Just to clarify, you are suggesting a new packet, e.g.
> qStr {addr},{maxlen}
> in response to which gdbserver will read up to either terminating NUL,
> or maxlen.
Ping?
Tom, is that what you had in mind?
Thanks,
--
Paul Pluzhnikov
next prev parent reply other threads:[~2011-07-19 17:22 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 [this message]
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
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=CALoOobM_+CJi3fWNk7C0K2ApRS76uRo9r6scDYCQnJHf8VSkBg@mail.gmail.com \
--to=ppluzhnikov@google.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.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