tech-toolchain archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Help needed with binutils solving [PR 54159]



The bug reported via PR 54159 with spurious warnings from GNU lib about
strings offsets past the size of the .strtab section are in fact due
to the fact that in the case of dynamic linking, the code takes the
.dynsym symbol table (and not the .symtab) and tries to match the offset
against .strtab while they are relative to .dynstr.

The warnings come from bfd_link_add_symbols(). But this is a generic
name and a backend version is called through the BFD xvec vector.

Since the backend is a assemblage of generic functions and special arm32
ones, it's difficult to find one's way through the maze.

My problem is to try to find which function is actually called and it
seems that the vectors are dynamically generated at config time and I'm
trying to find some text version (a header or a C file) but to no avail.

Does someone know how the xvec are defined and how to find what function
is actually called from sources without resorting to object file
processing---since the vectors are finally in a dso object
'lib/libbfd/targets.pico'. But I'm not a believer and don't believe that
it happens just due to the intervention of the holy spirit (mildly
holy considering the cascade of macro processing and post-processing
done... More on the devilish side, indeed).
-- 
        Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
                     http://www.kergis.com/
                       http://www.sbfa.fr/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C


Home | Main Index | Thread Index | Old Index