* Strange symbol binding type for basic_string::_Rep::_S_empty_rep_storage
@ 2013-01-11 15:22 Florian Weimer
2013-01-11 15:27 ` Ángel González
0 siblings, 1 reply; 3+ messages in thread
From: Florian Weimer @ 2013-01-11 15:22 UTC (permalink / raw)
To: gcc-help
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?
--
Florian Weimer / Red Hat Product Security Team
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Strange symbol binding type for basic_string::_Rep::_S_empty_rep_storage
2013-01-11 15:22 Strange symbol binding type for basic_string::_Rep::_S_empty_rep_storage Florian Weimer
@ 2013-01-11 15:27 ` Ángel González
2013-01-11 17:27 ` Florian Weimer
0 siblings, 1 reply; 3+ messages in thread
From: Ángel González @ 2013-01-11 15:27 UTC (permalink / raw)
To: Florian Weimer; +Cc: gcc-help
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Strange symbol binding type for basic_string::_Rep::_S_empty_rep_storage
2013-01-11 15:27 ` Ángel González
@ 2013-01-11 17:27 ` Florian Weimer
0 siblings, 0 replies; 3+ messages in thread
From: Florian Weimer @ 2013-01-11 17:27 UTC (permalink / raw)
To: Ángel González; +Cc: gcc-help
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2013-01-11 15:27 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-01-11 15:22 Strange symbol binding type for basic_string::_Rep::_S_empty_rep_storage Florian Weimer
2013-01-11 15:27 ` Ángel González
2013-01-11 17:27 ` Florian Weimer
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).