On 01/11/2013 04:20 PM, Ángel González wrote:
On 11/01/13 13:00, Florian Weimer wrote:
Some versions of libstdc++ (in Fedora 18) create symbol references to
_ZNSs4_Rep20_S_empty_rep_storageE@GLIBCXX_3.4 with an ELF binding type
of LOOS+0 (according to eu-readelf).
What causes this on the libstdc++ side? What would be a better name
for the binding type?
$ c++filt _ZNSs4_Rep20_S_empty_rep_storageE
std::basic_string<char, std::char_traits<char>, std::allocator<char>
::_Rep::_S_empty_rep_storage
It's an static empty string set all to 0s.
See /usr/include/c++/*/bits/basic_string.tcc
That's the definition. I'm just curious what causes the reference to
the symbol to have this strange LOOS+0 (vendor extension) symbol binding
type.
Hmm. I've got a theory. STB_LOOS+0 is STB_GNU_UNIQUE, so the GNU ELF
extension detection just doesn't work in this case. This is a property
of the DSO, and probably not related to libstdc++.
--
Florian Weimer / Red Hat Product Security Team
