Does purify always need to instrument the exe file and all the dlls that it uses, or is it possible to specify which dlls to skip? I have a set of plugin dlls that I would like to run under Purify as part of a very large application. The application loads dozens of other dlls that I do not care about. Unfortunately, one of these dlls is not instrumented correctly and the whole application fails before any of my dlls are being loaded. When I run the application on its own, it runs fine, but when I run it under purify, one of its instrumented dlls generates an unhandled null pointer exception and the whole thing terminates.
I tried to remove the culprit dll from the instrumentation list by going to Run Program\Settings\Power Check\Module Instrumentation. It lets me remove it, but when I run it, it reinstruments it all over again and adds it back to the module list. Any suggestion?
Thanks in advance
Pinned topic How to partially instrument a large application by Purify
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-12-03T23:17:21Z at 2012-12-03T23:17:21Z by SystemAdmin
Re: How to partially instrument a large application by Purify2012-12-03T21:00:20ZThis is the accepted answer. This is the accepted answer.Hi Nikita,
> Does purify always need to instrument the exe file and all the
> dlls that it uses?
The answer varies from platform to platform. It looks like you're
on Windows. The default behavior on Windows is to instrument the
EXE and all DLLs. The only option in your case is to use Purify's
"Selective Instrumentation" option:
In theory, this option allows you to instrument JUST your DLL and
ignore everything else. However, read over the Tech Note carefully.
There are some limitations and restrictions, and you will have to
rebuild your DLL.
Re: How to partially instrument a large application by Purify2012-12-03T23:17:21ZThis is the accepted answer. This is the accepted answer.
- SystemAdmin 110000D4XK