Fix gcc 2.95.3 Type Info Functions

[bonefish]

Currently the type info functions for __si_type_info and __class_type_info generated by gcc 2.95.3 are calling the base class(es) type info function(s), but instead of using the return value, refer to the base class type info(s) separately. This can cause problems with shared objects generated by older compilers (e.g. the BDirectWindow type info in libgame.so), since they can contain a type info without a type info function and a type info function of a library loaded later could therefore use the uninitialized one from the old library.

A fact contributing to the problem is that everything is linked with -Bsymbolic (thus disabling symbol preemption), which makes a type info function always initialize and return the type info defined in the same shared library instead of one defined in a library loaded earlier.

The place where to fix the bug is gcc/cp/rtti.c. expand_si_desc() is responsible for creating __si_type_info and expand_class_desc() for __class_type_info type info functions.

The naive approach to move the "get_typeid_1(type)" into the "elems" initialization in expand_si_desc() doesn't work, BTW.

[scottmc]

Was this worked on in the recent gcc update?

[bonefish]

Replying to scottmc:

Was this worked on in the recent gcc update?

Nope.

[bonefish]

#6963 is another instance of this problem.

[bonefish]

(In #6963) The main cause is that KISSlib.so has apparently been built under BeOS. It contains a type info for std::exception, but no type info function. This triggers the issue described in #1259.

The likely reason why the issue didn't show in earlier revisions is the second part of hrev39375. It's actually not even directly related to the weak symbol or symbol preemption features. It just changes the symbol resolution order to one that should be somewhat more robust when add-ons are involved. It could be reverted for gcc 2, but that would only fix this particular situation and might break using your library in a different situation instead. So I don't think there's much point in doing that.

Possible solutions for your problem:

• Preferred: Fixing #1259.
• Rebuilding KISSlib.so under Haiku.
• Could work: Build your application under BeOS. This would trigger Haiku's runtime loader's compatibility mode which might work around the issue.

Closing as duplicate of #1259.

[korli]

(In #8133) I suspect it's a duplicate of #1259