public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Luis Machado <luis.machado@linaro.org>
To: joel@rtems.org, gdb@sourceware.org
Subject: Re: 64-bit Addresses in remote protocol
Date: Mon, 22 Mar 2021 14:32:24 -0300	[thread overview]
Message-ID: <edb40cd5-6cd3-4653-2b77-efd8c4a04957@linaro.org> (raw)
In-Reply-To: <CAF9ehCVeyX72x3FePs0HgToqxizUU5cO_4ggba9FsS0gRPzX+Q@mail.gmail.com>

Hi,

On 3/22/21 1:55 PM, Joel Sherrill wrote:
> Hi
> 
> Over at RTEMS, we are looking at some warnings in our debug
> server and wondering if fields described as "addr" in the gdb
> protocol should be treated 64-bits when that target has 64-bit
> addresses like the aarch64.

If the inferior is using 64-bit addresses, then the remote protocol will 
also use 64-bit addresses. If we have a 32-bit inferior running on 
aarch64 hardware, we'll have 32-bit addresses over the remote protocol 
as well.

Even when we're using 64-bit addresses, the remote protocol may not pad 
it with zeroes to make it 64-bit, but it should still be handled as 64-bit.

Does that help?

> 
> Technically, we are looking at sweeping through our gdb server
> and using  uintptr_t for addresses where uint32_t has been
> ok before.
> 
> But I wanted to make sure that our assumption that "addr" means
> a valid target address which means it can be 32- or 64- bits based
> on the target.
> 
> Thanks.
> 
> --joel
> RTEMS
> 

  reply	other threads:[~2021-03-22 17:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-22 16:55 Joel Sherrill
2021-03-22 17:32 ` Luis Machado [this message]
2021-03-22 17:38   ` Joel Sherrill
2021-03-22 17:52     ` Luis Machado

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=edb40cd5-6cd3-4653-2b77-efd8c4a04957@linaro.org \
    --to=luis.machado@linaro.org \
    --cc=gdb@sourceware.org \
    --cc=joel@rtems.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).