This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: objcopy fails for Win64
- From: Nick Clifton <nickc at redhat dot com>
- To: NightStrike <nightstrike at gmail dot com>
- Cc: Binutils <binutils at sourceware dot org>, Kai Tietz <Kai dot Tietz at onevision dot com>, Kai Tietz <ktietz70 at googlemail dot com>
- Date: Mon, 07 Jul 2008 16:57:18 +0100
- Subject: Re: objcopy fails for Win64
- References: <b609cb3b0806250816g64611232o1c11fcc1546b2f63@mail.gmail.com>
Hi NightStrike,
Can someone help us debug why the simple objcopy test fails for the
target x86_64-pc-mingw32?
Executing on build: cmp tmpdir/testprog.exe tmpdir/copyprog (timeout = 300)
tmpdir/testprog.exe tmpdir/copyprog differ: byte 137, line 2
tmpdir/testprog.exe tmpdir/copyprog differ: byte 137, line 2
Have you looked at the differing byte (or bytes if it turns out that
there is more than one of them) ? Try running readelf and objdump on
the two binaries and comparing the outputs. If that does not show up
the reason for the discrepancy then you will have to generate a hex dump
up to offending byte and then try to debug the meaning of the bytes by
hand. The problem almost always turns out to be:
* An uninitialized byte in a header which gets written to disk.
* A timestamp.
* A 32-bit assumption tripping up on a 64-bit machine.
Cheers
Nick