Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Christo <christo.crause@gmail.com>
To: gdb@sourceware.org
Cc: christo.crause@gmail.com
Subject: Re: internal-error: target_xfer_partial: Assertion `*xfered_len > 0' failed
Date: Sat, 02 Jun 2018 06:23:00 -0000	[thread overview]
Message-ID: <1527920583.28838.13.camel@gmail.com> (raw)
In-Reply-To: <1527827775.28838.7.camel@gmail.com>

On Fri, 2018-06-01 at 06:36 +0200, Christo wrote:
> On Wed, 2018-05-30 at 22:09 +0200, Christo wrote:
> > 
> > I get this error both on avr-gdb 7.10.1 (Installed by Linux Mint) and gdb 8.0 (which I
> > compiled
> > from source).  I don't see this error if I don't load the file with debug info into gdb.
> > Also
> > no
> > error if I use gdb 7.0.1 or 6.6 (both also compiled by me).
> I tested on gdb 8.1 compiled for AVR and still see "Saw new packet start in middle of old one"
> message, but now gdb seems to ignore the packet error and just continue without the internal
> error message.  I still would like to know where the problem is so that it can be fixed, else
> gdb may end up with incomplete information of the flash memory content on the controller.

I suspect that the culprit was on my server side, where I transmitted responses as Pascal
strings, which prepends the length of the string to the data stream.  I suspect that gdb
filtered out the extra data at the start of the replies successfully in many (but not all)
cases.  Anyway, sending the replies as byte streams without a length prefix seems to have
eliminated my problem.


      reply	other threads:[~2018-06-02  6:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-30 20:09 Christo
2018-06-01  4:36 ` Christo
2018-06-02  6:23   ` Christo [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=1527920583.28838.13.camel@gmail.com \
    --to=christo.crause@gmail.com \
    --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