copy_private_bfd_data in bfd/elf.c question
Andreas Schwab
schwab@suse.de
Sat Jun 29 10:30:00 GMT 2002
Reva Cuthbertson <reva@cup.hp.com> writes:
|> A fix that we came up with is to disable the code
|> that sets p_paddr in copy_private_bfd_data(). We did
|> this and it worked fine. The other thing I noticed
|> is that the alignment specification for .hash is 8.
|> We never check this value when calculating file
|> position because that is only done of the section's
|> flags include SEC_ALLOC which is not the case with
|> the .hash section.
That looks odd. The secion flags of .hash include SHF_ALLOC, which
should be translated to SEC_ALLOC in BFD. If .hash isn't SEC_ALLOC then
something is wrong here.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
More information about the Binutils
mailing list