This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: PATCH fix start-time and stop-time in trace-status


On 10/16/12 8:15 AM, Pedro Alves wrote:
On 10/16/2012 03:59 PM, Dmitry Kozlov wrote:
Hi Tom,
Pedro already asked to rewrite this patch at gdbserver-side and use hex instead of decimal.
See http://sourceware.org/ml/gdb-patches/2012-10/msg00193.html
Could you setup one common opinion about what way is right?
Since the RSP uses hex everywhere, the argument for keeping decimal format because
it's human-readable in the remote log doesn't really hold.  Instead, having different
formats makes reading the logs _worse_ (forcing one to wonder "is this in hex, or
in decimal").  Given that there's no backwards compatibility issue here, I much
prefer fixing gdbserver.


Yes, it looks like it was simply a brain cramp on my part, I was probably thinking plongest put out hex digits and didn't notice because the times printed on the host looked plausible.


(Ironically, a decimal-point encoding would probably be the most futureproof, right now the protocol assumes timestamps are in microseconds and a target reporting in nanoseconds would either lose data or cause all kinds of confusion.)

Stan
stan@codesourcery.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]