--- Additional Comments From hjl at lucon dot org 2007-03-29 14:50 ---
I guess
LDFLAGS=-s
-Wl,-O1,-zdynsort,-z,combreloc,-hashval,--as-needed,--enable-new-dtags -Bdirect
doesn't work with your linker. I have no problems on FC6:
bash-3.1$ cat x.c
#include
int
main ()
{
printf ("Hell
Hi Sami,
Right, first of all, I have checked in the patch as it currently
exists (patch.5). We will be branching for release 2.18 at some point
in the near future and I want to make sure that the error checking we
have already developed gets into that release. I added this ChangeLog
entry
--- Additional Comments From nickc at redhat dot com 2007-03-29 16:01
---
Subject: Re: Broken object file crashes nm
Hi Sami,
Right, first of all, I have checked in the patch as it currently
exists (patch.5). We will be branching for release 2.18 at some point
in the near future
--- Additional Comments From nickc at redhat dot com 2007-03-29 16:01
---
Created an attachment (id=1655)
--> (http://sourceware.org/bugzilla/attachment.cgi?id=1655&action=view)
Add another check for a NULL idx->shdr entry.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=4110
--
--- Additional Comments From hjl at lucon dot org 2007-03-29 17:04 ---
It works for me. Please provide a QMAGIC file which shows the problem.
--
What|Removed |Added
--- Additional Comments From Quentin dot Godfroy at ens dot fr 2007-03-29
17:17 ---
Created an attachment (id=1656)
--> (http://sourceware.org/bugzilla/attachment.cgi?id=1656&action=view)
QMAGIC sample
This sample was created with as and ld configured with host=x86_64-linux and
target=
--- Additional Comments From hjl at lucon dot org 2007-03-29 17:35 ---
That is normal since bfd_vma is 64bit on 64bit host. The same applies to any
32bit targets, including ELF/i386.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=4292
--- You are receiving this mail because: -
--- Additional Comments From nickc at redhat dot com 2007-03-29 17:41
---
Created an attachment (id=1657)
--> (http://sourceware.org/bugzilla/attachment.cgi?id=1657&action=view)
Make nm print addresses of symbols as 32-bit or 64-bit values, depending upon
the size of the target
--
--- Additional Comments From hjl at lucon dot org 2007-03-29 18:16 ---
It is not just nm. Almost all programs in binutils behave the same when
displaying address, either for output or error message. We should be
very careful, not to hide problems. For example, when nm shows
...
--- Additional Comments From nickc at redhat dot com 2007-03-29 18:16
---
Created an attachment (id=1658)
--> (http://sourceware.org/bugzilla/attachment.cgi?id=1658&action=view)
Improved version of previous patch with better heuristics for guessing target
address size
--
W
Hi Quentin,
target=i486-linuxaout.
The problem here is that the aout file format does not specify the
address size of the objects it contains, so the BFD library does not
know whether the objects are 32-bit or 64-bit. Instead nm defaults to
using the bitsize of the host.
I have uploaded
--- Additional Comments From nickc at redhat dot com 2007-03-29 18:17
---
Subject: Re: nm and objdump show addresses on 64 bits
for32bit a.out files
Hi Quentin,
> target=i486-linuxaout.
The problem here is that the aout file format does not specify the
address size of the objec
--- Additional Comments From Quentin dot Godfroy at ens dot fr 2007-03-29
19:35 ---
(In reply to comment #7)
> Subject: Re: nm and objdump show addresses on 64 bits
> for 32bit a.out files
>
> > target=i486-linuxaout.
>
> The problem here is that the aout file format does not specif
13 matches
Mail list logo
