From: "Erik Niessen" <erik.niessen@gmail.com>
To: gdb@sourceware.org
Subject: Re: inconsistency in printing out the value of an unsigned short in gdb
Date: Wed, 26 Sep 2007 08:33:00 -0000 [thread overview]
Message-ID: <f21fe8a50709260035x242d655ew1c45b194a6000da9@mail.gmail.com> (raw)
In-Reply-To: <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
>
next prev parent reply other threads:[~2007-09-26 7:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 14:19 Erik Niessen
2007-09-25 15:57 ` Daniel Jacobowitz
2007-09-26 8:33 ` Erik Niessen [this message]
2007-09-26 21:38 ` Daniel Jacobowitz
2007-09-27 11:27 ` Erik Niessen
2007-09-27 12:15 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f21fe8a50709260035x242d655ew1c45b194a6000da9@mail.gmail.com \
--to=erik.niessen@gmail.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox