AppVerifier is a very useful tool when it comes to finding memory leaks. It is relatively easy to configure if you have some understanding of how AKU's and PB work. There are pretty comprehensive instructions on MSDN found here. However if you need to use AppVerifier on something that loads during boot time, you need to perform extra steps that are harder to find. The purpose of this article is to explain in a greater detail what you need to do to setup AppVerifier for processes that load at boot time.
Here are simple steps that you need to follow to make AppVerifier work for "Always Running" processes:
1. Install Platform Builder (tools only install is enough because CETK is included with that install), install AKU if you haven't already2. Open your AKU build window where you build images3. (Optional) Removed/reset all the security or make sure it's configured properly4. Copy all the AppVerifier binaries to your %_FLATRELEASEDIR% by running getappverif_cetk.bat from your wcetk directory.
If you are connected with KITL the log file with AppVerifier information can be found in your release directory it should be called something like this AppVerifier_<ProcessName>_<ProcessIdentifier>.log older versions of AppVerifier might call it VerifierLog_<AppName_<ProcessIdentifier>.log
Thanks for pointing this out.
But one small correction: instead of SET VERIFY_MODULE= it should be SET VERIFY_MODULES=
and also its makeimg.bat instead of makeimg.exe
Also have a doubt,
when i tried running makeimg, there was an error saying:
SignTool Error: File not found: shimeng.dll
Could you help me?