From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: Pedro Alves <palves@redhat.com>
Cc: Christian Groessler <chris@groessler.org>, gdb@sourceware.org
Subject: Re: remote packet size for memory read
Date: Wed, 24 Jul 2013 23:00:00 -0000 [thread overview]
Message-ID: <1374706819.3495.12.camel@soleil> (raw)
In-Reply-To: <51D6D745.4040505@redhat.com>
On Fri, 2013-07-05 at 15:25 +0100, Pedro Alves wrote:
> 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.
Problem of GDB asking to read packetsize/2 has also be detected with
the Valgrind gdbserver, which expects that
nr_bytes_requested_in_m_packet*2 + 4 <= packetsize
but GDB only guarantees
nr_bytes_requested_in_m_packet*2 <= packetsize
> If you don't plan on contributing fixes, could you file (separate) bug
> reports for these, so they don't get lost?
Have these been filed ? Not seen ...
>
> Thanks,
next prev parent reply other threads:[~2013-07-24 23:00 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
2013-07-24 23:00 ` Philippe Waroquiers [this message]
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=1374706819.3495.12.camel@soleil \
--to=philippe.waroquiers@skynet.be \
--cc=chris@groessler.org \
--cc=gdb@sourceware.org \
--cc=palves@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