This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: PATCH fix start-time and stop-time in trace-status
- From: Pedro Alves <palves at redhat dot com>
- To: Dmitry Kozlov <dmitry_kozlov at mentor dot com>
- Cc: Tom Tromey <tromey at redhat dot com>, gdb-patches at sourceware dot org, "'Stan_Shebs at mentor dot com'" <Stan_Shebs at mentor dot com>, Vladimir Prus <vladimir at codesourcery dot com>
- Date: Tue, 16 Oct 2012 16:15:28 +0100
- Subject: Re: PATCH fix start-time and stop-time in trace-status
- References: <506444DD.9040503@mentor.com> <87d317wlaa.fsf@fleche.redhat.com> <50699D74.2090401@mentor.com> <87mwzna6u3.fsf@fleche.redhat.com> <507D7654.90206@mentor.com>
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.
> It would very kind of you if you can look at other 2 related patches.
I'm looking at them now.
--
Pedro Alves