From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9456 invoked by alias); 20 Jan 2004 19:10:09 -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 9442 invoked from network); 20 Jan 2004 19:10:02 -0000 Received: from unknown (HELO bilbo.inter.net.il) (192.114.186.18) by sources.redhat.com with SMTP; 20 Jan 2004 19:10:02 -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 CGE18566; Tue, 20 Jan 2004 21:09:26 +0200 (IST) Date: Tue, 20 Jan 2004 19:10:00 -0000 From: "Eli Zaretskii" To: Andrew Cagney Message-Id: <9003-Tue20Jan2004210551+0200-eliz@elta.co.il> CC: drow@mvista.com, gdb-patches@sources.redhat.com In-reply-to: <400D5C3E.9000100@gnu.org> (message from Andrew Cagney on Tue, 20 Jan 2004 11:50:06 -0500) Subject: Re: [RFC]: remove inconsistency in printcmd.c: print_scalar_formatted Reply-to: Eli Zaretskii References: <3FDA26B1.6010704@redhat.com> <1031212221704.ZM22539@localhost.localdomain> <3FDA636F.30204@redhat.com> <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> <400D5C3E.9000100@gnu.org> X-SW-Source: 2004-01/txt/msg00559.txt.bz2 > Date: Tue, 20 Jan 2004 11:50:06 -0500 > From: Andrew Cagney > > Try: > > (gdb) x 1.0 > 0x000001: 0x12345678 > (gdb) x/v 1.0 > 0x000000: 0xc0000000 > > or more notably: > > (gdb) print struct_val > { i = 1, j = 2, k = 1.0 } > (gdb) info location struct_val > struct_val is a dwarf2 location expression, its value is scattered > across memory and registers > (gdb) x/v struct_val > 0x00000000: 0x00010002 0xc0000000 Andrew, are you saying that "x/v" is already in GDB and does everything Daniel asked for? Anyway, I don't find the /v specifier in the manual. Is this implemented, or is this just a suggestion for a new feature?