From: Simon Marchi <simon.marchi@polymtl.ca>
To: Jeff Wandling <JWandling@blueorigin.com>
Cc: gdb@sourceware.org
Subject: Re: [EXTERNAL] Re: Debugging big-endian ARM target from little-endian host
Date: Sun, 03 Mar 2019 01:48:00 -0000 [thread overview]
Message-ID: <29e028e71ea334d4b74553ff8c704691@polymtl.ca> (raw)
In-Reply-To: <0d0fafabebda4de28cd415f0a9b5d7ce@MAIL01.blueorigin.com>
On 2019-03-01 17:15, Jeff Wandling wrote:
> Yes, I am using -endian big with JLinkGDBServer
Ok.
I tested remote-debugging a big-endian machine (gcc110.fsffrance.org) to
see how registers are actually transmitted. I confirm that they are
transmitted in big endian form. This would mean that JLinkGdbServer is
indeed at fault. I would suggest contacting Segger's support at this
point.
Simon
next prev parent reply other threads:[~2019-03-03 1:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 19:50 Jeff Wandling
2019-02-28 14:02 ` Simon Marchi
2019-03-01 19:45 ` Jeff Wandling
2019-03-01 21:54 ` Simon Marchi
2019-03-01 22:15 ` [EXTERNAL] " Jeff Wandling
2019-03-03 1:48 ` Simon Marchi [this message]
2019-03-03 17:38 ` Jeff Wandling
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=29e028e71ea334d4b74553ff8c704691@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=JWandling@blueorigin.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