[omniORB] omniORB 4.0.3 (vxWorks) stuck in tcpTransport initialization

Duncan Grisby duncan at grisby.org
Mon Apr 25 20:05:11 BST 2005


On Tuesday 19 April, "Kiesswetter, Florian (Florian)" wrote:

> we use omniORB 4.0.3 for vxWorks and I expect a bug in the tcp
> transport initialization in the case if there are interfaces which
> don't have the flag IFF_UP.
>
> Below are the suspect lines out of the file tcpTransportImplc.cc in
> the function "void vxworks_get_ifinfo(omnivector<const char*>&
> ifaddrs)" (line 406).
>
> If an interface in the list is not UP this part will not be evaluated,
> and the entryLength and the pointer to the ifreq struct will not be
> modified and hence not set to the next interface.
>
> -> omniORB will continue in an endless loop for this not running
> interface. I think the last brace should be moved up 2 lines.

Thanks for reporting the bug. I've fixed it in cvs.

Cheers,

Duncan.

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



More information about the omniORB-list mailing list