[omniORB] proxyObjectFactory for shared components

[Duncan Grisby]

On Tuesday 20 November, "Renzo Tomaselli" wrote:

> then if any such component is unloaded at runtime then the application
> crashes as soon as any involved interface is instantiated. This occurs since
> the related proxyObjectFactory is unloaded from memory thus leaving a
> dangling pointer around (in orbcore/proxyObjectFactory.cc).
> While all of this is true for 3.04, I would like to know about 4.0: any plan
> to fix this behavior or is there anything I might do for that ? (the basic
> point is to keep track of factory indentities, so that their destructors
> should remove the right one from the orb list).

The proxyObjectFactory code hasn't changed in omniORB 4, so at the
moment it's the same as omniORB 3. If you can come up with a patch
that does what you want in a thread-safe and clean manner, I'll think
about incorporating it.

Cheers,

Duncan.

-- 
 -- Duncan Grisby  \  Research Engineer  --
  -- AT&T Laboratories Cambridge          --
   -- http://www.uk.research.att.com/~dpg1 --