[EMAIL PROTECTED] (Lukas Schlosser) writes:
> I posted the attached mail on February 2nd, 2000 - but I didn't get
> any response till now. I have to reach a decision, please help me!
> Due to the fact, that this is the only gdb newsgoup I found, I hope
> that you can name me a correct contact person to find the answer
> onto the following urgent questions:
If I understand your problem correctly, I don't think that GDB can do
what you want it to.
A little endian cross-GDB on a host can communicate with a big endian
target (and vice versa). This can be done for both "live" systems or
crash/core dumps (although GDBs support for non-native crash dumps is
not really there, it's not difficult to do if you are willing to hack
GDB itself).
But you seem to want is the ability of a native (host == target)
little endian GDB to interpret a data stream generated on a big endian
target by loading that data into memory with a program under debug and
then examining it.
You might be able to make do by writing some GDB user defined functions
to interpret the data. These functions could do the byte swapping, and
even pretty-print the data structures. It wouldn't be too difficult
to do, but it would be more or less the same work as writing a stand-
alone program to do the same thing.
--jtc
--
J.T. Conklin
RedBack Networks
