From: Nick Clifton <nickc@redhat.com>
To: David Lecomber <david@allinea.com>
Cc: binutils@sources.redhat.com
Subject: Re: XCOFF 64 function address wrong?
Date: Wed, 09 Mar 2005 12:53:00 -0000 [thread overview]
Message-ID: <422EF4B5.2000204@redhat.com> (raw)
In-Reply-To: <1110356435.7150.2.camel@cpc2-oxfd5-5-0-cust103.oxfd.cable.ntl.com>
Hi David,
> I have a 64-bit AIX 5.2 XLC 7 compiled hello world binary. I've built
> up gdb and binutils with --enable-64-bit-bfd - from latest CVS.
>
> In GDB, it miscalculates the main(), as 0x428 (instead of 0x10000428).
This looks like a truncation to 32-bits rather than a more general
miscalculation...
> So, in using a fresh binutils's "objdump -t":
> [ 89](sec 1)(fl 0x00)(ty 20)(scl 2) (nx 2) 0x00000428 .main
> Note the 0x0000428 .main,
> I'm willing to put some time in to getting this sorted out, but at
> present don't know what I'm looking for -- so any help greatly
> appreciated.
Have a look at the function coff_print_symbol() in bfd/coffgen.c. This
is the function that is printing out the incorrect value for .main. My
guess is that for some reason XCOFF64 is not defined for your
configuration and so it is printing a 32-bit value instead of a 64-bit
value.
Cheers
Nick
next prev parent reply other threads:[~2005-03-09 12:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 8:14 David Lecomber
2005-03-09 12:53 ` Nick Clifton [this message]
2005-03-09 14:54 ` David Lecomber
2005-03-09 15:39 ` Nick Clifton
2005-03-09 17:52 ` David Lecomber
2005-03-10 10:22 ` Nick Clifton
2005-03-10 21:56 ` David Lecomber
2005-03-11 10:37 ` Nick Clifton
2005-03-24 2:03 ` David Lecomber
2005-04-04 16:19 ` Nick Clifton
2005-04-15 11:49 ` Nick Clifton
2005-05-16 17:07 ` David Lecomber
2005-05-17 13:04 ` Nick Clifton
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=422EF4B5.2000204@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=david@allinea.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).