[omniORB] unexpected Python exception during up-call

[Duncan Grisby]

On Tuesday 3 June, Jian Wu wrote:

> During execution, a unexceped execption is caught at the python servant side
> and displayed on the screen:
> 
> -------------------------------------------------------------------------------------------------------------
> 
> omniORB: Caught an unexpected Python exception during up-call.
> 
> TypeError: 'NoneType' object is not callable
> 
> ---------------------------------------------------------------------------------------------------------------
> 
> However, no logging of tracebacks makes debugging impossible. We use omniorb
> 4.1.0 and omniorbPy 3.0.

In what context?  If an exception occurs there should usually be a
traceback. What happens if you run with -ORBtraceLevel 25
-ORBtraceInvocations 1  ?

Duncan.

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