From: Luis Machado <luis.machado@linaro.org>
To: Reinoud Koornstra <reinoudkoornstra@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: gdb 8.3.1 truncated register in remote g packet
Date: Sat, 02 Nov 2019 01:30:00 -0000 [thread overview]
Message-ID: <1b1ebf11-3e2c-d5b3-6a5b-50ed54e791bc@linaro.org> (raw)
In-Reply-To: <CAAA5faH6L30J9VGLdnjqvWbtsp4HpB1woQc0knFjh5f1k0USAg@mail.gmail.com>
Hi,
On 11/1/19 6:05 PM, Reinoud Koornstra wrote:
> Hi Luis,
> The remote platform is arm32. Weirdly enough, when I use a gdb 7.7
> compiled only for x86_64, it does seem to work a bit better, no clue
> exactly why.
I'm not sure why an arm-targeted gdb would not complain about loading a
x86-target vmlinux image. That sounds off.
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.
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.
Just to confirm, does your arm target have floating point registers?
next prev parent reply other threads:[~2019-11-02 1:30 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 [this message]
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=1b1ebf11-3e2c-d5b3-6a5b-50ed54e791bc@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