Re: Instrumenting provider code with purifyplus

Devchandra L Meetei <[email protected]> Fri, 1 Mar 2013 12:16:23 +0530
Newsgroups gmane.network.open-pegasus.general
Message-ID <CAKmFMKe5H8-ww6DgHvNxrERUpPZFqWDJz4hfy6ZCR1Cmm6Jrcw@mail.gmail.com>
Have not done much in Windows,
In Linux with valgrind, personally I prefer writing a unit test which tests
all the functionality of the provider and run test under valgrind tracing
all the child
-- 
Warm Regards
--Dev
OpenPegasus Developer/Committer
"It's Always better to try and fail instead of not doing/trying anything"


On Fri, Mar 1, 2013 at 12:07 PM, Vijayalakshmi Subramanyam <
[email protected]> wrote:

> Hi,
>
>
>
> I am trying to use purifyplus on a windows x64 machine to check for any
> memory leaks within our provider.
>
>
>
> When i try to instrument cimprovagt.exe , i do not see my code being
> instrumented for memory leaks. I see all pegasus dlls being instumented.
>
>
>
> Should i build my provider as a standalone application for this ? If so,
> could you suggest me the steps.
>
>
>
> Regards,
>
>
>
> Vijayalakshmi
>