[haiku-development] Re: BeOS Apps Crashing on Haiku (Bug #889)

Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx> wrote:
> Besides ignoring the problem I see the following possible solutions:
> 
> 1) Modify our runtime loader to use the same symbol resolution 
> strategy as 
> Be's. This should fix the problem for all executables (running on 
> BeOS) 
> that suffer from it. As mentioned before, I believe, our current 
> runtime 
> loader behavior is more correct, though.
> 
> 2) Modify the gcc type info functions to use the type_info returned 
> by the 
> base class type info function instead of resolving it separately. 
> This 
> makes sure the type_info used has been initialized. The change should 
> fix 
> e.g. the file panel problem several of the Be applications have, but 
> -- 
> since we only correct the type info functions in our code -- it might 
> not 
> fix all instances of the problem.
> 
> Opinions?

Nice problem we ran into there :-)
I would actually think it would be best to implement both options; 1) 
because it'll definitely solve the problem and makes us compatible with 
BeOS - we could make the change a compiler option - and 2) because it's 
more elegant, anyway :-)

Also, what about the thread safety problem in the initialization? Is 
that easily solvable? And if not, what could happen in the worst case?

Bye,
   Axel.

Other related posts: