Re: Memory leak analysis with valgrind

Since providers are shared libraries, you could easily check for memory leaks 
with a fake main program that simply make a series of function calls to all the 
provider entry points.  I don't see why Pegasus would matter in terms of 
checking for memory leaks.

 
Portland, OR 97231




________________________________
From: "Prager, Faina" <[email protected]>
To: [email protected]
Sent: Thu, July 15, 2010 2:53:33 PM
Subject: Memory leak analysis with valgrind

 
Hello,
 
I am trying to test our providers for memory leaks using valgrind, but the 
latest version of valgrind does not seem to work with OpenPegasus, has some 
threading issues.  The patch for Valgrind 2.0.0 produces the : “true: symbol 
lookup error: /usr/lib/valgrind/valgrind.so: undefined symbol: __libc_accept” 
error.
 
Is there any way to test providers with valgrind using Pegasus?
 
Thank you,
Faina Prager