[Orbit-python-list] Exception handling inside C modules.

[Dominik <du...@fa...>]

Hello everyone.


For last few days I've been trying to wrap some libOAF functions for use
with

Python. Everything went flawlessly until it came to execption handling.
libOAF

calls just return plain CORBA_Evironment and it would be best to just
behave as

if the call was made in orbit-python, that is raise python exception 

created by orbit-python during parsing of oaf.idl (import OAF). 

Therefore I exposed check_corba_ex function into public header (patch
included).

The problem is that calling it from my module causes python to SEGV soon
after.

Is there any special semantics connected with this function? Or maybe
there is

some better way of dealing with CORBA exceptions in C python modules?

Regards,
Domink.