[omniORB] feature or bug? - pointer to returned value is null

[Adrian Rosoga]

> That should never happen.

Indeed, it was my fault. I had a proxy that caught ORB
exceptions in some situations and returned a null
pointer. Sorry for that.

Regards,
Adrian

--- Duncan Grisby <duncan@grisby.org> wrote:
> On Wednesday 26 March, Adrian Rosoga wrote:
> 
> > I would like to know in what circumstances the
> return
> > value (the pointer to the returned structure) from
> a
> > remote method is null. The returned value is a
> pointer
> > to a structure containing variable length data.
> See
> > the code at the end of the message.
> 
> That should never happen.
> 
> [...]
> > I'm using omniORB4 on a Solaris machine (SunOs
> 5.8).
> > Everything compiled with Forte. CORBA is quite
> > intensively used, the machine is at his limits. It
> > looks like the problem is more likely to occur if
> the
> > machine is overloaded.
> 
> Variable length structs are allocated on the heap,
> so it's possible
> that the allocation with new would fail and return
> zero, due to
> running out of memory. However, if that happened,
> you would expect a
> segfault when the unmarshalling code tried to fill
> in the members of
> the struct.
> 
> Please run with -ORBtraceLevel 25. That might print
> out some
> information that shows what's going wrong.
> 
> Cheers,
> 
> Duncan.
> 
> -- 
>  -- Duncan Grisby         --
>   -- duncan@grisby.org     --
>    -- http://www.grisby.org --


__________________________________________________
Do you Yahoo!?
Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
http://platinum.yahoo.com