public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Jon Wilson <jonwilson030981@googlemail.com>
To: gdb@sourceware.org
Subject: Fwd: GDB Stub with ARM BE8 target.
Date: Tue, 31 May 2022 10:38:28 -0400	[thread overview]
Message-ID: <d8b7ffe2-cd4f-26ac-277e-9c50400c9036@gmail.com> (raw)
In-Reply-To: <b49371fd-9a4e-1d4f-78b9-dcb54e93fd3d@gmail.com>

I am trying to integrate a GDB stub with a ARM BE8 target. However, it 
would appear that using "set endian big" defaults to BE32 architecture. 
I cannot seem to find a way to have the debugger interpret memory 
according to the BE8 architecture. The only support for BE8 mode I can 
see seems to be for when using BE8 core dumps or processes 
(https://github.com/bminor/binutils-gdb/blob/9606310bbbf8a2d529b5c2aa71cac48a46f65869/gdb/arm-tdep.c#L9781). 
I can't seem to find any documentation on the topic (which is pretty 
forgivable given how niche it is).

I looked at handling the endianness in the stub itself (e.g. inverting 
the endianness of memory based on permissions), but given the code 
stream can contain both instructions (which should be little endian in 
BE8) as well as data (which should be interpretted as big endian), this 
is not possible.

Have I missed an option somewhere? If this support is missing, then how 
should it be added? Should it be handled in a similar way to how GDB 
handles ARM versus Thumb mode? 
(https://github.com/bminor/binutils-gdb/blob/9606310bbbf8a2d529b5c2aa71cac48a46f65869/gdb/arm-tdep.c#L10589)?

I'd be very grateful for any advice.

Kind Regards.


Jon


  reply	other threads:[~2022-05-31 14:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-30 23:03 Jon Wilson
2022-05-31 14:38 ` Jon Wilson [this message]
2022-06-01  8:55 ` 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=d8b7ffe2-cd4f-26ac-277e-9c50400c9036@gmail.com \
    --to=jonwilson030981@googlemail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).