InteractiveAugmentedIOException in CUT sc_ucalc

[Henrik /KaarPoSoft]

On 02/13/2013 05:41 PM, Stephan Bergmann wrote:
> On 02/13/2013 04:46 PM, Tor Lillqvist wrote:
>>> so that some catch block that should match doesn't.
>>
>> Isn't one typical problem that two type_infos are compared for
>> equality by comparing the name string pointers instead of comparing
>> the name strings with strcmp? I have seen stuff like that both in the
>> Android and iOS ports, I think. Unfortunately it is such a complex
>> topic that I don't recall the details. But yeah, there must be
>> something special in his toolchain compared to that on "normal" Linux.
>
> Comparing just pointers is indeed how the g++ runtime traditionally
> behaved---though that's been changed in more recent times, to actually
> compare the strings.  That's the reason why LO has traditionally been
> careful to export all the weak _ZTI* and _ZTS* symbols from all libraries.
>
> Stephan
>

I have only very limited knowledge of the LO codebase and inner 
workings, and I have no clue what "C++ UNO bridge" is or how it works.

Any hints on what I could do to debug / investigate this further would 
be most appreciated.

/Henrik