Application Verifier on Drivers; Windows Mobile 6

re: Application Verifier on Drivers; Windows Mobile 6

yubaolee@gmail.com — Wed, 16 Dec 2009 01:47:40 GMT

quote PK:

0x1e011dd0: UNKNOWN!UNKNOWN + 00011dd0h

0x1e01197c: UNKNOWN!UNKNOWN + 0001197ch

0x1e011bc8: UNKNOWN!UNKNOWN + 00011bc8h

I came across this probolem too.

re: Application Verifier on Drivers; Windows Mobile 6

RK — Thu, 06 Mar 2008 02:27:54 GMT

I have used AppVerifier to verify my device.exe with KITL and FRD several times, and most of them are very successful. However, I found that sometimes they failed because the callstack could NOT be resolved. The KITL message I saw in the output window of PB5 is as follows:

===

Couldn't resolve address 0x027ef244 (138521)

Couldn't resolve address 0x1e011dd0 (138521)

Couldn't resolve address 0x1e01197c (138521)

Couldn't resolve address 0x1e011bc8 (138521)

===

and in the target window after I run "heapverif * delta" is

===

TrackedItem count: 1

Callstack:

0x07a46b78: shim_heap.dll!(null) + 6b78h

0x07a4984c: shim_heap.dll!(null) + 984ch

0x07a4abbc: shim_heap.dll!(null) + abbch

0x07a4accc: shim_heap.dll!(null) + accch

0x027ef244: UNKNOWN!UNKNOWN + 027ef244h

0x03f55f90: devmgr.dll!(null) + 3f90h

0x03f57298: devmgr.dll!(null) + 5298h

0x03f54254: devmgr.dll!(null) + 2254h

0x03f74c18: coredll.dll!(null) + 16c18h

0x1e011dd0: UNKNOWN!UNKNOWN + 00011dd0h

0x1e01197c: UNKNOWN!UNKNOWN + 0001197ch

0x1e011bc8: UNKNOWN!UNKNOWN + 00011bc8h

0x03f7b368: coredll.dll!(null) + 1d368h

Leaked items:

0x00b68800 16 bytes, thread: 0xc712f152, checkpoint 1

Total: 16 bytes

===

As you see, many "UNKNOWN" shown in the callstack. And then I could NOT know where it is.

Sometimes I face this problem, even my friend also face this problem. Do you have any idea why this happen?

re: Application Verifier on Drivers; Windows Mobile 6

Paul Sheh — Mon, 28 Jan 2008 18:25:04 GMT

Recently I started using App Verifier to catch memory leaks in our platform and have everything working with KITL and access to the FRD, however, I'm seeing the same thing as a post above, i.e., it complains that verify.txt cannot be found. I verified that it is indeed in the \windows directory, both by using image-explorer and by letting the device boot (which takes a long time since everything seems to be shimmed in the absence of verify.txt). Any ideas? Thanks.

re: Application Verifier on Drivers; Windows Mobile 6

mthomps — Wed, 01 Aug 2007 19:58:56 GMT

Motanis, sorry for the delayed response. I've been on a much needed vacation. I'll need more information. Are the files added to common.bib actually visable in the \windows directory of the booted device? You should see appverif.exe, lmemdebug.dll, shim_heap.dll, verify.tx and all of the other files added to common.bib.

re: Application Verifier on Drivers; Windows Mobile 6

Motanis — Fri, 20 Jul 2007 12:52:37 GMT

Hi Mike, Thanks for your article. The first method "Testing with KITL and the FRD" is quite smooth by following your description. But I got a problem when i try the second method- "Testing with KITL but without access to FRD" , all all and txt in common.bib has embedded into my image file beside lmemdebug.dll , surly i has this file in my release folder, and sign it by add commend in premakeimg.bat. I can't not figure it out what's wrong outthere! Any suggestion? Thanks in advance

Motanis

re: Application Verifier on Drivers; Windows Mobile 6

mthomps — Tue, 26 Jun 2007 20:24:37 GMT

Jack,

I'm afraid I'm at a bit of a loss, but to answer some specific questions with quotes from some experts on the topic:

1. No you can't disable the Load/unload library; if you did, dynamic api redirection wouldn't work (the app would do an end-run around app verifier).

2. lmemdebug.dll is loaded by coredll

Is this a platform you are building, or are you trying to apply this to a platform built by someone else?

Mike

re: Application Verifier on Drivers; Windows Mobile 6

mthomps — Tue, 26 Jun 2007 18:42:57 GMT

Wow, it doesn't pay to let blogs sit; my apologies.

Running app verifier on device.exe is not a good idea. You effectively run app verifier on every driver and the amount of data will make it difficult to get meaninful results. Pick "suspect" drivers and focus on them. You'll notice in my example I shimed camera.dll. I then performed actions to specifically exercise that driver. And what you want to do is to perform repetitive exercises of the driver; because drivers don't close, the first time they are exercised they may reserve memory that they never free. App verifier will suspect a leak. But repeat this process over and over. If additional memory is consumed each time; you likely have a leak.

Mike

re: Application Verifier on Drivers; Windows Mobile 6

shyhlee — Fri, 15 Jun 2007 12:26:10 GMT

I am puzzled for one question in here: While doing Hopper test, how can we use appverify to figure out any memory leak in the driver?

For example, I set a check point before hopper test as: "heapverif device.exe delta"

After hopper stop, I do "heapverif device.exe delta".

The list will be long and I an not sure if it make sense for us to analysis it.

Appreciate for any comments or suggestions.

By the way, is there any way to disable callstack dump while doing delta?

re: Application Verifier on Drivers; Windows Mobile 6

Jack Wong — Thu, 10 May 2007 19:59:07 GMT

Hi Mike,

Another problem is that who loads the lmemdebug.dll? it's too early for it to load because the filesys's API are not ready. So it must be some way to delay of the loading of the lmemdebug to make it successful.

Thank you.

Jack

re: Application Verifier on Drivers; Windows Mobile 6

Jack Wong — Wed, 09 May 2007 17:51:22 GMT

Hi Mike,

I am pretty sure that the verify.txt is in image and in oemxipkernel package. Just don't know why it can't find it at very early stage. I have another questions, it seems that the shimverifier.dll also checks something other than I specified such as load/unload library. Can I disable it? Thanks,

Jack