This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
Re: remote/2301: Transmission gdb gdbserver remotestub corrupted
- From: Daniel Jacobowitz <drow at false dot org>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 14 Aug 2007 12:18:02 -0000
- Subject: Re: remote/2301: Transmission gdb gdbserver remotestub corrupted
- Reply-to: Daniel Jacobowitz <drow at false dot org>
The following reply was made to PR remote/2301; it has been noted by GNATS.
From: Daniel Jacobowitz <drow@false.org>
To: "Hagge, Nils" <nils.hagge@siemens.com>
Cc: "Neugebauer, Manfred" <manfred.neugebauer@siemens.com>,
gdb-gnats@sourceware.org
Subject: Re: remote/2301: Transmission gdb gdbserver remotestub corrupted
Date: Tue, 14 Aug 2007 08:15:47 -0400
On Tue, Aug 14, 2007 at 01:34:58PM +0200, Hagge, Nils wrote:
> This means that the checksum is generated, after the first bytes "Hc"
> are
> Destroyed, since F8+20+2D+31 = 176 --> mod 256 --> 76 (see above!). As a
> Coincidence the checksum checking fails, nevertheless, since in the
> remote stub
> The checksum is calculated from the 7-bit values --> F8 is treated as
> 78,
> Thus on the target 78+20+2D+31 = F6 is compared to 76, which generates a
>
> "bad checksum" error.
>
> Do you want me to prepare a more detailed log?
No, I want evidence of _what_ is destroying the buffer. If the
checksum is being generated after the bytes are corrupted then
this can't have anything to do with TCP since the packet has not been
sent yet.
I suggest you try a current snapshot of GDB instead of the
cygwin-special version.
--
Daniel Jacobowitz
CodeSourcery