[omniORB] OmniORB 4.0.3 and Valgrind

[Michael Shearer]

Duncan,

The uninitialised memory reads are the only ones I've stumbled on so far as well.  I was just wondering if there were others that I had maybe not encountered yet.  But since you are using Valgrind, no problem then! :)

Cheers,

Mike

-----Original Message-----
From: Duncan Grisby [mailto:duncan at grisby.org]
Sent: Monday, April 12, 2004 4:11 PM
To: Michael Shearer
Cc: omniorb-list at omniorb-support.com
Subject: Re: [omniORB] OmniORB 4.0.3 and Valgrind 


On Monday 12 April, "Michael Shearer" wrote:

> Has anyone ever used Valgrind against applications that use omniORB?

Yes. I regularly check omniORB with valgrind.

> I've recently been testing my code against Valgrind =
> (http://valgrind.kde.org); a GPL application similar to Purify.  It's
> found a few bugs in the ORB core of my application.  The bugs aren't
> major but they could lead to unexpected behaviour.  Has anyone ever
> though of using it against omniORB in the hopes of making it even more
> robust?

What bugs has it found?  The only thing I've seen it reporting are
uninitialised memory reads for padding bytes used in GIOP messages.
They are harmless, and not a bug.

Cheers,

Duncan.

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