This is the mail archive of the
mailing list for the GDB project.
RE: Debugging big-endian ARM target from little-endian host
- From: Jeff Wandling <JWandling at blueorigin dot com>
- To: "gdb at sourceware dot org" <gdb at sourceware dot org>
- Date: Fri, 1 Mar 2019 19:45:40 +0000
- Subject: RE: Debugging big-endian ARM target from little-endian host
- References: <firstname.lastname@example.org>
From: Simon Marchi <email@example.com>
Sent: Thursday, February 28, 2019 6:02 AM
To: Jeff Wandling <JWandling@blueorigin.com>
Subject: Re: Debugging big-endian ARM target from little-endian host
Do "set debug remote 1" and then "continue" so that you hit your breakpoint. Towards the end of the debug output, you should see a vCont;c packet, with a "stop reply" packet (assuming JLink supports the vCont packet, and you use the all-stop mode). Here's an example with
Sending packet: $vCont;c:p209a.-1#da...Packet received:
In the response, you can see a few pairs of register number/register values. Since you know the PC you expect your program to stop at, it should be fairly easy to spot the PC register. The value should be in big endian, in your case. In my case, 10:0c46555555550000 corresponds to the PC value in little endian:
(gdb) p $pc
$1 = (void (*)()) 0x55555555460c <main+4>
If you have trouble interpreting the debug remote output, pastebin it and send the link.
The interesting result was the JLinkGDBServer doesn't emit the "vCont" packet unless I am misreading the result.
I'm boxed into a corner since I have a SEGGER JLink dongol and so choosing to use JLinkGDBServer is not arbitrary.