Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Reinoud Koornstra <reinoudkoornstra@gmail.com>
To: Luis Machado <luis.machado@linaro.org>
Cc: gdb@sourceware.org
Subject: Re: gdb 8.3.1 truncated register in remote g packet
Date: Sun, 03 Nov 2019 00:07:00 -0000	[thread overview]
Message-ID: <CAAA5faHpGYZoUXd=Yh2jXbMyTZLKnUcGgLnLHVJWPMaETfqkcQ@mail.gmail.com> (raw)
In-Reply-To: <1b1ebf11-3e2c-d5b3-6a5b-50ed54e791bc@linaro.org>

>
>
> I'm not sure why an arm-targeted gdb would not complain about loading a
> x86-target vmlinux image. That sounds off.
>
> The vmlinux was compiled for arm, the thing that surprised me that the x64
gdb didn't complain about it. The arm gdb didn't complain either which was
logical.


> You could try with an older arm gdb to see if it works fine. If it does
> and the latest version doesn't, then we may need to investigate it.
>
Ok, I'll compile and older gdb for arm and let you know.

>
> I checked the code and the truncation message is a result of the
> debugging stub sending less bytes than GDB expects for the register set.
>
> The interesting thing is that the incompatible gdb for x86-64 was able to
read the message and the gdb for arm wasn't, but i'll try with an older gdb
for arm, but it's weird.


> Just to confirm, does your arm target have floating point registers?
>
Good point, I did assume it has, because in some cases armeabihf was used
to compile, but not in all cases, I'll check whether it is, otherwise I'd
have to recompile gdb without hf.
I'll get the info and let you know, thanks for helping out!

Reinoud.


  reply	other threads:[~2019-11-03  0:07 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
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 [this message]
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='CAAA5faHpGYZoUXd=Yh2jXbMyTZLKnUcGgLnLHVJWPMaETfqkcQ@mail.gmail.com' \
    --to=reinoudkoornstra@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=luis.machado@linaro.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