Hi all,

This is a rework of a patch I submitted last autumn. I have updated it 
to fit with the new convenience variable preservation and rethought the 
requirements.

The patch fixes up the endian of all integer and pointer internal 
variables and leaves all other types alone.

My understanding is that an internal variable cannot contain anything 
other than a built-in type. Any other value is merely a memory 
reference. Indeed, value_of_internalvar() goes out of it's way to ensure 
that values loaded from memory are never saved long term. The result is 
that there is no point in attempting to do anything with the endian of 
these values because they will always be of the same endian as the 
target/program being debugged.

The upshot is that, although it is possible to contrive an example [1] 
that causes gdb to print values in the wrong endian, in the normal case, 
in which the user does not change the endian except upon connection to 
the target, the values will always be presented as they expect. 
Including internal variables written prior to connection.

[1] Once connected to the target, write data in endian A, create a 
variable referencing that data, type 'set endian B' and the print the 
data - it comes out reversed.

If I have something wrong here please point it out.

Thanks

Andrew Stubbs