Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Luis Machado <luis.machado@linaro.org>
To: Reinoud Koornstra <reinoudkoornstra@gmail.com>, gdb@sourceware.org
Subject: Re: gdb 8.3.1 truncated register in remote g packet
Date: Fri, 01 Nov 2019 16:11:00 -0000	[thread overview]
Message-ID: <5c9d0ab7-4e03-ea43-ae54-5d2aed0728e0@linaro.org> (raw)
In-Reply-To: <CAAA5faFwCD9xVgJFFpdc8WXaDWVPpQ6_O7gFchVHp6-a9k0bsA@mail.gmail.com>

Hi Reinoud,

On 10/31/19 3:58 PM, Reinoud Koornstra wrote:
> Hello Everyone,
> 
> I downloaded an compiled gdb 8.3.1 with --target=arm-linux-gnueabihf on my
> x86_64 pc.
> Compiled and installed fine. I started the gdb with the vmlinux file and
> tried to connect to the remote arm32 machine: target remote /dev/ttyUSB0
> Then I get: Truncated register 19  in remote 'g' packet.
> What is going wrong here? I saw earlier archives about similar issues, but
> i thought those would have been patched. Any help would be appreciated.
That error means your remote arm32 machine's debugging stub doesn't 
agree with GDB in terms of the register set. GDB is likely assuming 
register set A and the debugging stub is assuming register set B.

You can check what the debugging stub is sending via "set debug remote 
1". If it supports XML register descriptions, you'll see data flying by.

If it doesn't, then GDB is probably making a guess as to what the proper 
register set is.

In summary, i think we need more data in order to make an informer guess 
on what is going wrong here, but probably GDB and the debugging stub are 
not in sync in terms of registers.

> Thanks,
> 
> Reinoud.
> 


  reply	other threads:[~2019-11-01 16:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-31 18:58 Reinoud Koornstra
2019-11-01 16:11 ` Luis Machado [this message]
2019-11-01 18:24   ` Reinoud Koornstra
2019-11-01 20:27     ` Luis Machado
2019-11-01 20:55       ` Reinoud Koornstra
2019-11-01 21:05         ` Reinoud Koornstra
2019-11-02  1:30           ` Luis Machado
2019-11-03  0:07             ` Reinoud Koornstra
2019-11-04 14:48               ` Luis Machado
2019-11-04 17:53                 ` Reinoud Koornstra
2019-11-05  0:50                   ` Luis Machado
2019-11-05  4:05                     ` Reinoud Koornstra
2019-11-05 11:33                       ` Luis Machado
2019-11-05 12:49                       ` Luis Machado
2019-11-05 18:50                         ` Reinoud Koornstra

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=5c9d0ab7-4e03-ea43-ae54-5d2aed0728e0@linaro.org \
    --to=luis.machado@linaro.org \
    --cc=gdb@sourceware.org \
    --cc=reinoudkoornstra@gmail.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