This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: PATCH: Put libunwind.a in libgcc_s.so: versioning of _Unwind_*() symbols
>>>>> On Wed, 21 Apr 2004 10:13:06 -0700, "H. J. Lu" <hjl@lucon.org> said:
HJ> The unwinder in gcc is C++ ABI-compliant.
No, it isn't. Not as long as it defines ABI-defined symbols as
versioned symbols. That means anything that got linked against
libgcc_s will never be able to use the ABI-defined symbols from
another library (such as libunwind).
>>>>> On Wed, 21 Apr 2004 10:13:06 -0700, "H. J. Lu" <hjl@lucon.org> said:
HJ> The unwinder in gcc is C++ ABI-compliant. But it doesn't mean
HJ> you can mix 2 unwind libraries together. As soon as you did
HJ> # g++ -shared ...
HJ> you may already have linked part of whatever unwind library gcc
HJ> is using into the resulting shared library. It won't be easy to
HJ> use another unwind library after that.
Nonsense. LD_PRELOAD=/usr/lib/libunwind.so would do just fine.
The problem isn't even libunwind-specific, as my example from
yesterday evening showed.
--david