From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32388 invoked by alias); 20 Jan 2004 20:32:01 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 32371 invoked from network); 20 Jan 2004 20:31:59 -0000 Received: from unknown (HELO bilbo.inter.net.il) (192.114.186.18) by sources.redhat.com with SMTP; 20 Jan 2004 20:31:59 -0000 Received: from zaretski (pns03-206-161.inter.net.il [80.230.206.161]) by bilbo.inter.net.il (Mirapoint Messaging Server MOS 3.3.8-GR) with ESMTP id CGE42132; Tue, 20 Jan 2004 22:31:23 +0200 (IST) Date: Tue, 20 Jan 2004 20:32:00 -0000 From: "Eli Zaretskii" To: Daniel Jacobowitz Message-Id: <1659-Tue20Jan2004222747+0200-eliz@elta.co.il> CC: cagney@gnu.org, gdb-patches@sources.redhat.com In-reply-to: <20040120193349.GA26311@nevyn.them.org> (message from Daniel Jacobowitz on Tue, 20 Jan 2004 14:33:49 -0500) Subject: Re: [RFC]: remove inconsistency in printcmd.c: print_scalar_formatted Reply-to: Eli Zaretskii References: <400C58E6.4070908@redhat.com> <400C60C0.9040702@gnu.org> <20040119231853.GA6132@nevyn.them.org> <400C7948.9060300@gnu.org> <20040120012252.GA4828@nevyn.them.org> <400C8CC0.3040706@gnu.org> <20040120054836.GA23548@nevyn.them.org> <2427-Tue20Jan2004085108+0200-eliz@elta.co.il> <20040120145225.GA10459@nevyn.them.org> <2719-Tue20Jan2004211055+0200-eliz@elta.co.il> <20040120193349.GA26311@nevyn.them.org> X-SW-Source: 2004-01/txt/msg00564.txt.bz2 > Date: Tue, 20 Jan 2004 14:33:49 -0500 > From: Daniel Jacobowitz > > I'll respond to these all together, since there's really the same > answer to all of them: I think there is a general unimplemented feature > here, not just the specific "show me the hex representation of this > double". Examples I have in mind: > - Displaying an integer to a sequence of characters > p/s 0x6263 -> "ab" > - Displaying a double-precision value in hex: > p/x 2.0 -> 0x4000000000000000 > - Displaying a double-precision value in binary: > p/t 2.0 -> 01000000000000000000000000000000 > 00000000000000000000000000000000 > - Displaying an integer (hex or otherwise) value as a double > p/f 0x4000000000000000LL -> 2.0 > - Displaying an integer (hex or otherwise) value as a long > double - this one is trickier, since we don't normally have an > integer type that is big enough, but if we did: > p/gf 0x400000000000000000000000LLL -> 2.0 Sounds like there's a place for a new command, since what we want here is a command that would interpret a value as some different type. Do you agree?