Exception handling as thrown from BPL so (was: Re: [C++-sig] Re: Loading Boost.Python made bindings is horribly slow?)

[Niall Douglas]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Related to my previous post, I am now finding that if I throw an 
exception from within my python extension module, the client program 
won't catch it. This has started happening since I implemented that 
symbol versioning trick previously suggested.

I'm guessing that the type info symbols are getting stripped and so 
it's unable to match the exception type with the catch type. Am I 
right in this? It's very hard to prove as it's a 130Mb shared object 
(this is *without* debug info) and it's horribly mangles my computer 
when running in gdb.

If I am right (please confirm), does anyone know how RTTI symbols are 
mangled precisely so I can keep them from getting stripped?

(Roll on declspec() for GCC!)

Cheers,
Niall





-----BEGIN PGP SIGNATURE-----
Version: idw's PGP-Frontend 4.9.6.1 / 9-2003 + PGP 8.0.2

iQA/AwUBQG8AucEcvDLFGKbPEQI83gCg9wdlBKZW6O4lcBOKU8TMHjKNEV0AoO7R
DTLo/iWNrZ5uOolZ2czIvc7E
=oPYE
-----END PGP SIGNATURE-----