From: Yao Qi <qiyaoltc@gmail.com>
To: toemoss garcia <toemossgarcia@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: ARM BE8 support is broken
Date: Fri, 20 Nov 2015 09:03:00 -0000 [thread overview]
Message-ID: <86twohyrdr.fsf@gmail.com> (raw)
In-Reply-To: <CALRw1GG+n38ADxzp9tqyPJr2BVD9vrvg-FnhQ5mGs7F76KAuwQ@mail.gmail.com> (toemoss garcia's message of "Thu, 19 Nov 2015 12:12:28 -0600")
toemoss garcia <toemossgarcia@gmail.com> writes:
Hi,
> There has been *some* support added for BE8 in GDB, but as far as
> I can tell, all the patches do is treat everything as BE and
> manually swap instructions to LE (see [2] for the patch
> submission). This only seems to effect doing a ``load`` or when
> reading a memory address as an instruction. There doesn't seem to
> be any actual support for correctly reading/writing memory based
> on the region of memory space. IOW, the only thing you can do
> reliably for BE8 is load a program to the core (this seems to
> always work correctly for BE8 images).
It is known that there are some bugs in GDB for ARM BE8.
>
> Is there anything in the works/any interest in getting this kind
> of support added?
Last year, Victor Kamensky from linaro posted some patches for ARM BE8,
and some patches were committed. However, looks he stopped working on
this. This is the only effort related to ARM BE8 which I am aware of.
>
> Does anybody have experience using BE8 with GDB? How did
> you "solve" this?
No, I don't have experience using BE8, all my arm boards are little
endian. If you want to fix them, patches are welcome. You can also
post your problems here, and people are happy to help you.
--
Yao (齐尧)
prev parent reply other threads:[~2015-11-20 9:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 18:12 toemoss garcia
2015-11-20 9:03 ` Yao Qi [this message]
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=86twohyrdr.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=gdb@sourceware.org \
--cc=toemossgarcia@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