This is the mail archive of the
mailing list for the GDB project.
Re: [RFC]: remove inconsistency in printcmd.c: print_scalar_formatted
- From: Andrew Cagney <cagney at gnu dot org>
- To: Daniel Jacobowitz <drow at mvista dot com>
- Cc: gdb-patches at sources dot redhat dot com
- Date: Mon, 19 Jan 2004 19:41:44 -0500
- Subject: Re: [RFC]: remove inconsistency in printcmd.c: print_scalar_formatted
- References: <3FDA26B1.email@example.com> <1031212221704.ZM22539@localhost.localdomain> <3FDA636F.firstname.lastname@example.org> <400C58E6.email@example.com> <400C60C0.firstname.lastname@example.org> <20040119231853.GA6132@nevyn.them.org>
On Mon, Jan 19, 2004 at 05:57:04PM -0500, Andrew Cagney wrote:
>Ping. Could we continue discussing this topic and come to some form of
>resolution? The new additional ia64 test failures are annoying.
I thought there was basic agreement with your change (It sux less then
the current behavior :-). Yes, change it. That way, behavior such as:
(gdb) print/x 1.0
will at least be more consistent.
Yeah, I agree, and re-reading Kevin's message I don't think he objects.
How do you all feel about a more sweeping change instead:
(gdb) set $doublevar = 2.0
(gdb) print doublevar
$1 = 2.0
(gdb) print (int) doublevar
$1 = 2
(gdb) print/x (int) doublevar
$1 = 2
(gdb) print/x doublevar
$1 = 0xc000000000000000
(gdb) print/i doublevar
???? [no preference really]
No. That would be wrong. print/<format> prints the value (not the
implementation) using the specified format. Being able to examine the
underlying implementation in various formats is more of an "examine"