From: Pedro Alves <palves@redhat.com>
To: Christian Groessler <chris@groessler.org>
Cc: gdb@sourceware.org
Subject: Re: remote packet size for memory read
Date: Fri, 05 Jul 2013 14:26:00 -0000 [thread overview]
Message-ID: <51D6D745.4040505@redhat.com> (raw)
In-Reply-To: <51D292E7.9040900@groessler.org>
On 07/02/2013 09:44 AM, Christian Groessler wrote:
I haven't analyzed the issue thoroughly, but it's quite plausible
you're right.
If you don't plan on contributing fixes, could you file (separate) bug
reports for these, so they don't get lost?
Thanks,
--
Pedro Alves
next parent reply other threads:[~2013-07-05 14:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51D29213.2050801@groessler.org>
[not found] ` <51D292E7.9040900@groessler.org>
2013-07-05 14:26 ` Pedro Alves [this message]
2013-07-24 23:00 ` Philippe Waroquiers
2013-07-25 7:07 ` Christian Groessler
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=51D6D745.4040505@redhat.com \
--to=palves@redhat.com \
--cc=chris@groessler.org \
--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