[omniORB] [4.0.6/Linux/C++] possibly invalid use of memory when UserException is returned

[Luke Deller]

Hi Slawomir,

On Tue, 2005-09-06 at 11:43 -0500, Slawomir Lisznianski wrote:
> I noticed that when a UserException is returned from a call, valgrind
> (v2.4.0) occasionally reports invalid use of memory. When I was testing
> a server which repeatedly returned exceptions, I was able to seg. fault
> it after a while. I'm not sure if server's crash is related to the
> valgrind's report, but so far that's the only hint I've got. 
> 
> ==22901==
> ==22901== Thread 6:
> ==22901== Syscall param socketcall.send(msg) points to uninitialised
> byte(s)
...

OmniORB does not initialise padding bytes in messages, which causes
valgrind warnings such as these.  This is normal, and doesn't help find
the source of your seg fault :-|

Luke.