[omniORB] Object refernce from JAVA Object implementation used in omniORB aborts the executable]

[David Morgenlender]

On Fri, 18 Dec 1998 15:11:43 +0000, you wrote:

>An exception is thrown but I have at the moment only the default used
>catch(...). The assertion comes from dbgheap.c of the MS debug lib and
>is
>called something like CrtlsValidHeapPointer.
>What other exception when calling the remote objects member is
>appropriate?

I don't know Java, but I've gotten this message in C++ when a parameter =
is
allocated anywhere but on the heap.  omniORB does a delete when it =
decides to
deallocate the parameter.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
Dave Morgenlender
e-mail: dmorgen@alum.mit.edu
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D