[lldb-dev] target and host with different endianness

[Philippe Lavoie via lldb-dev]

We have a big-endian target that we debug from LLDB running on Windows through a custom process plugin and communication protocol.

The target's default byte order is set to eByteOrderBig in 'g_core_definitions' in ArchSpec.cpp.

Most features work correctly (registers, variables, breakpoints, disassembly), but expressions seem to ignore arch endianness:

For example:

(lldb) reg read pc
      pc = 0x00400020  arithmetic.elf`main + 32 at main.c:12
(lldb) expr -f hex -- $pc
(unsigned int) $2 = 0x20004000
(lldb)

Has this scenario (big-endian target and little-endian host) been tested/used ?

Thanks,
-Philippe
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20160211/771618ef/attachment.html>