[omniORB] valgrind reports errors in omniORB 4.0.6

[Duncan Grisby]

On Monday 16 May, "Slawomir Lisznianski" wrote:

> How serious are the following errors reported by valgrind 2.4.0 against
> omniORB-4.0.6:

Not at all serious...

> ==1688== Syscall param socketcall.sendto(msg) points to uninitialised
> byte(s)
> ==1688==    at 0x48EF9F28: sendto (in /lib/tls/libc-2.3.5.so)
> ==1688==    by 0x48F1678F: getifaddrs (in /lib/tls/libc-2.3.5.so)
> ==1688==    by 0x1BE37E23: omni::ifaddrs_get_ifinfo(omnivector<char
> const*>&) (in /custom/usr/local/omniORB-4.0.6/lib/libomniORB4.so.0.6)

This is the platform's getifaddrs call that is failing to initialise
something, not an issue in omniORB.

> ==1688== Syscall param socketcall.send(msg) points to uninitialised
> byte(s)
> ==1688==    at 0x49162888: send (in /lib/tls/libpthread-2.3.5.so)
> ==1688==    by 0x1BDF3C6F:
> omni::giopStream::sendChunk(omni::giopStream_Buffer*) (in
> /custom/usr/local/omniORB-4.0.6/lib/libomniORB4.so.0.6)

This is just uninitialised padding bytes in the GIOP messages omniORB
sends. Nothing to worry about. All the other warnings are the same.

Cheers,

Duncan.

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