Exceptions across shared libraries (gcc 3.3.3)

[gilles.rayrat]

Hi,
I am facing a weird issue:
We are using a shared library (libcarob) that can throw exceptions.
Everything goes well under most platforms, but under suse (SLES 9, gcc
3.3.3), we get a segfault anytime we try to throw an exception out of
carob.
The weird thing is that when linking statically carob to the libstdc++,

the problem disappears. Google showed nothing convincing, so I try
other
channels...
If anyone has a clue for it, g++ flags or whatever, I am ready to try
the hell to fix this
Thanks,
Gilles.

[mlimber]

gi***********@gmail.com wrote:

Hi,
I am facing a weird issue:
We are using a shared library (libcarob) that can throw exceptions.
Everything goes well under most platforms, but under suse (SLES 9, gcc
3.3.3), we get a segfault anytime we try to throw an exception out of
carob.
The weird thing is that when linking statically carob to the libstdc++,

the problem disappears. Google showed nothing convincing, so I try
other
channels...
If anyone has a clue for it, g++ flags or whatever, I am ready to try
the hell to fix this

You'll want to post in a group for g++ and/or your troublesome
platform. Standard C++ knows nothing of static vs. dynamic linking, so
that is off-topic here
(http://www.parashift.com/c++-faq-lit....html#faq-5.9).

Cheers! --M