This is the mail archive of the gdb@sourceware.org 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: inconsistency in printing out the value of an unsigned short in gdb

From: "Erik Niessen" <erik dot niessen at gmail dot com>
To: gdb at sourceware dot org
Date: Wed, 26 Sep 2007 09:35:55 +0200
Subject: Re: inconsistency in printing out the value of an unsigned short in gdb
References: <f21fe8a50709250710i75147c23o5015a81e3a470a78@mail.gmail.com> <20070925141947.GA6437@caradoc.them.org>

Hi Daniel,

Thanks for your fast reply. I tried with different versions of g++
(3.4.6, 4.0, 4.0.4) they all have the same problem.
Is there a way how I can check the produced debug info for example via objdump?
So that I can convince the g++ people otherwise they will point their
finger at gdb.

Cheers,

Erik

On 9/25/07, Daniel Jacobowitz <drow@false.org> wrote:
> On Tue, Sep 25, 2007 at 04:10:51PM +0200, Erik Niessen wrote:
> > Any ideas??
>
> Probably inaccurate debug information from your compiler, and
> different generated code.  The value has been extended for some reason
> before GDB got a chance to print it.
>
> --
> Daniel Jacobowitz
> CodeSourcery
>

Follow-Ups:
- Re: inconsistency in printing out the value of an unsigned short in gdb
  - From: Daniel Jacobowitz

References:
- inconsistency in printing out the value of an unsigned short in gdb
  - From: Erik Niessen
- Re: inconsistency in printing out the value of an unsigned short in gdb
  - From: Daniel Jacobowitz

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