[omniORB] Uncaught Python exception in omniORBpy raised by a C extension

[Duncan Grisby]

On Thursday 6 January, "Scott Yang" wrote:

> Looking at the source, I found PyErr_Fetch(&etype, &evalue,
> &etracekback) has been used to analyse the caught exception. However,
> since exceptions raised by extensions do not instantiate, "evalue" would
> be NULL and omniORBpy would just treat it as an unexpected Python
> exception. The patch attached adds PyErr_NormalizeException() right
> after PyErr_Fetch() to defeat the lazy-instantiation of Python
> exception. It has no speed penalty if the exception has already been
> instantiated (raised inside Python).

Thanks for the patch. I've checked it in.

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan at grisby.org     --
   -- http://www.grisby.org --