detecting leaks with purify in shared libraries

[julian...@gmail.com]

Hello.

On my solaris 10 box, I have a propriety application (no source code),
which dynamically links my shared library (I have the source).
How can I use purify to detect leaks in the plug-in (shared library)?

when tried, purify says something like (cant paste the exact snipped
at the moment):
"appName appears to be complete executable, cannot be instrumented."

Thanks in advance, Julian

[Eric Sosman]

I don't know how to do it with Purify, or whether it's
even possible -- maybe an IBM/Rational forum would have an
answer. But since you're on Solaris, you might be able to
use the built-in libumem.so to detect leaks. There are a
couple of blogs describing how to substitute libumem.so for
the default allocator at run-time, and how to specify how
much and what kind of debugging information you want.

--
Eric Sosman
eso...@ieee-dot-org.invalid

[julian...@gmail.com]

> > How can I use purify to detect leaks in the plug-in (shared library)?

> But since you're on Solaris, you might be able to
> use the built-in libumem.so to detect leaks.  

Hi Eric.
Thanks for the answer, I already tried libumem and mdb. Its useful
indeed, but Purify has different approach (instrumenting the code),
thus some scenarios looks easier to deal with when levaraging Purify.

Any other hints?

Regards, Julian.

[Eric Sosman]

Just the one I already offered: Try an IBM/Rational forum
(or support channel).

--
Eric Sosman
eso...@ieee-dot-org.invalid

[Scott Lurndal]

Write your own application that uses the library and purify them both together.

scott