This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: regression with huge integer

From: Mark Kettenis <kettenis at chello dot nl>
To: schwab at suse dot de
Cc: mec dot gnu at mindspring dot com, gdb at sources dot redhat dot com, jjohnstn at redhat dot com
Date: Mon, 23 Feb 2004 22:26:08 +0100 (CET)
Subject: Re: regression with huge integer
References: <20040223195548.B7CDD4B104@berman.michael-chastain.com> <jek72dle8e.fsf@sykes.suse.de>

   From: Andreas Schwab <schwab@suse.de>
   Date: Mon, 23 Feb 2004 21:42:25 +0100

   mec.gnu@mindspring.com (Michael Elizabeth Chastain) writes:

   > But with the recent simplification to print_scalar_formatted, gdb
   > HEAD says:
   >
   >   (gdb) print int256var
   >   $1 = 0x0000002a0000002b0000002c0000002d0000002d0000002c0000002b0000002a
   >   (gdb) print /x int256var
   >   $2 = That operation is not available on integers of more than 8 bytes.

   That looks like gdb is contradicting itself.  It can print in hex, but
   then asked to print in hex it cannot. :-)

So this test uncovers a genuine bug.  Therefore, we shouldn't adjust
the testsuite.

Mark

References:
- regression with huge integer
  - From: Michael Elizabeth Chastain
- Re: regression with huge integer
  - From: Andreas Schwab

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]