[omniORB] Potential bug with "empty" valuetype in OmniPy [C1]

[Duncan Grisby]

On Tuesday 26 May, Stephane BONNIEZ wrote:

[...]
> I have a server started, exposing TestService, and I try to call it, so I
> instantiate a CompositeType. That's where I get into trouble. If either
> obj1 or obj2 is left to None, everything goes all right but if they both
> have a not-None value, the client crashes with the following error message:
> 
>     omniORB: Assertion failed.  This indicates a bug in the application
>     using omniORB, or maybe in omniORB itself.
>      file: cdrValueChunkStream.cc
>      line: 286
>      info: *endp == -(pd_nestLevel + 1)
>     omniORB: Unexpected C++ exception during Python invocation.

It is indeed a bug. The chunked valuetype encoding did not properly
handle the case of a value with no data. I've fixed it in CVS. Note that
the fix is in omniORB, not in omniORBpy, so you need to update omniORB
to get the fix.

Cheers,

Duncan.

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