From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12671 invoked by alias); 16 Oct 2012 17:07:15 -0000 Received: (qmail 12654 invoked by uid 22791); 16 Oct 2012 17:07:13 -0000 X-SWARE-Spam-Status: No, hits=-3.3 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from elasmtp-spurfowl.atl.sa.earthlink.net (HELO elasmtp-spurfowl.atl.sa.earthlink.net) (209.86.89.66) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 16 Oct 2012 17:07:09 +0000 Received: from [68.96.200.16] (helo=macbook2.local) by elasmtp-spurfowl.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from ) id 1TOAbl-0002OP-0R for gdb-patches@sourceware.org; Tue, 16 Oct 2012 13:07:09 -0400 Message-ID: <507D942C.5010302@earthlink.net> Date: Tue, 16 Oct 2012 17:07:00 -0000 From: Stan Shebs User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121010 Thunderbird/16.0.1 MIME-Version: 1.0 To: gdb-patches@sourceware.org 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> <507D7A10.1060202@redhat.com> In-Reply-To: <507D7A10.1060202@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: ae6f8838ff913eba0cc1426638a40ef67e972de0d01da9404868e51446b1edf8e9c4f4206471ff31350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2012-10/txt/msg00255.txt.bz2 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