From reviewer's point of view, I'd like each patch series is
self-contained and independent. Your patch series is about supporting
software breakpoint, software single step and tracepoint in ARM linux
GDBserver. Why do we need to worry about the different endianness of
GDBserver and inferior in your patch series? Your code may be right,
and we may need them sooner or later, but we can't do all of them in one
go.
Alright, here's what I propose in this case, since we may need this
support at one point but we do not now.
I could keep the shared breakpoints definitions , shared operation
signatures and other context that carries the endianness.
(Note that most of this context/signatures just can't go away since it
GDB needs it and the code is shared. )
But I will remove the BE8 detection and ELF endianness detection from
GDBServer.
So this way while the architecture of GDBServer will be able to handle
it from the start the feature itself won't be until a separate patch.
Does that sound ok ?