Application verifier to test drivers - Software-Testing

Hi, Joseph,

Here's a pretty comprehensive article on this subject that should guide you
through this process:
http://blogs.msdn.com/hopperx/archiv...-mobile-6.aspx

--Marty Larson [MS]

"joseph" <joseph@discussions.microsoft.com> wrote in message
news:39038ED9-C061-40EC-8B7D-7C44BC7C5494@microsoft.com...
> Hi All,
> I've read the procedure to use application verifier to test drivers from
> the
> link:http://msdn2.microsoft.com/en-us/library/aa463113.aspx.
> After following all the steps & OS boot, how to invoke Application
> verifier
> to test "mydriver.dll"(a sample stream driver created for test)? this
> procedure is not clear.
> Also, why do i need tux.exe/device.exe in :set VERIFY_MODULES=tux.exe
> device.exe mydriver.dll ?

Dear Marty,
Thanks a lot for the wonderful link.
I want to insert shims to "mydriver.dll".
But, I'm getting PB debug messages as follows during booting:
1660 PID:83fa2b3a TID:83fa2b0a Shim autoloader: launching appverif.exe -m
{all} -s shim_heap.dll
1810 PID:23f99aaa TID:23f99bb2 Shim autoloader: being loaded into app
verifier binary
1820 PID:23f99aaa TID:23f99bb2 Loading shim 'shim_heap.dll'
2050 PID:23f99aaa TID:23f99bb2 Shim_heap: Loaded into process
'appverif.exe'
2130 PID:23f99aaa TID:23f99bb2 Applying shim 'shim_heap.dll' to module
'{all}'
2180 PID:23f99aaa TID:23f99bb2 Loading shim 'shim_verifier.dll'
2290 PID:23f99aaa TID:23f99bb2 Applying shim 'shim_verifier.dll' to
module '{all}'
2300 PID:23f99aaa TID:23f99bb2 Enabling shim engine...
2410 PID:23f99aaa TID:23f99bb2 Verifier loader: SUCCESS


---> Here, I expected "Applying shim 'shim_verifier.dll' to module
'mydriver.dll'".But why it is applying for "{all}"?
When I run makeverifyfile.bat, it's giving following messages:
Setting shims to apply: shim_heap.dll
Setting verify options: NoMapFiles EnableFanOut IgnoreNullFree
Setting modules to verify: mydriver.dll
Done creating automatic shim file!
Renaming lmemdebug_autoshim to lmemdebug...

which shall confirm that:set VERIFY_MODULES=mydriver.dll is properly
set.But, why it is happening for {all} modules during booting?


"Marty Larson" wrote:

> Hi, Joseph,
>
> Here's a pretty comprehensive article on this subject that should guide you
> through this process:
> http://blogs.msdn.com/hopperx/archiv...-mobile-6.aspx
>
> --Marty Larson [MS]
>
> "joseph" <joseph@discussions.microsoft.com> wrote in message
> news:39038ED9-C061-40EC-8B7D-7C44BC7C5494@microsoft.com...
> > Hi All,
> > I've read the procedure to use application verifier to test drivers from
> > the
> > link:http://msdn2.microsoft.com/en-us/library/aa463113.aspx.
> > After following all the steps & OS boot, how to invoke Application
> > verifier
> > to test "mydriver.dll"(a sample stream driver created for test)? this
> > procedure is not clear.
> > Also, why do i need tux.exe/device.exe in :set VERIFY_MODULES=tux.exe
> > device.exe mydriver.dll ?
>
>
>

Hi, Joseph,

The output of makeverifyfile.bat is a file named verify.txt. It sounds like
that file isn't being opened and parsed correctly. Can you double-check that
it's available in your release directory?

--Marty Larson

"joseph" <joseph@discussions.microsoft.com> wrote in message
news:0F4B35AC-4E63-4970-B020-AA35D1D6C53D@microsoft.com...
> Dear Marty,
> Thanks a lot for the wonderful link.
> I want to insert shims to "mydriver.dll".
> But, I'm getting PB debug messages as follows during booting:
> 1660 PID:83fa2b3a TID:83fa2b0a Shim autoloader: launching appverif.exe -m
> {all} -s shim_heap.dll
> 1810 PID:23f99aaa TID:23f99bb2 Shim autoloader: being loaded into app
> verifier binary
> 1820 PID:23f99aaa TID:23f99bb2 Loading shim 'shim_heap.dll'
> 2050 PID:23f99aaa TID:23f99bb2 Shim_heap: Loaded into process
> 'appverif.exe'
> 2130 PID:23f99aaa TID:23f99bb2 Applying shim 'shim_heap.dll' to module
> '{all}'
> 2180 PID:23f99aaa TID:23f99bb2 Loading shim 'shim_verifier.dll'
> 2290 PID:23f99aaa TID:23f99bb2 Applying shim 'shim_verifier.dll' to
> module '{all}'
> 2300 PID:23f99aaa TID:23f99bb2 Enabling shim engine...
> 2410 PID:23f99aaa TID:23f99bb2 Verifier loader: SUCCESS
>
>
> ---> Here, I expected "Applying shim 'shim_verifier.dll' to module
> 'mydriver.dll'".But why it is applying for "{all}"?
> When I run makeverifyfile.bat, it's giving following messages:
> Setting shims to apply: shim_heap.dll
> Setting verify options: NoMapFiles EnableFanOut IgnoreNullFree
> Setting modules to verify: mydriver.dll
> Done creating automatic shim file!
> Renaming lmemdebug_autoshim to lmemdebug...
>
> which shall confirm that:set VERIFY_MODULES=mydriver.dll is properly
> set.But, why it is happening for {all} modules during booting?
>
>
> "Marty Larson" wrote:
>
>> Hi, Joseph,
>>
>> Here's a pretty comprehensive article on this subject that should guide
>> you
>> through this process:
>> http://blogs.msdn.com/hopperx/archiv...-mobile-6.aspx
>>
>> --Marty Larson [MS]
>>
>> "joseph" <joseph@discussions.microsoft.com> wrote in message
>> news:39038ED9-C061-40EC-8B7D-7C44BC7C5494@microsoft.com...
>> > Hi All,
>> > I've read the procedure to use application verifier to test drivers
>> > from
>> > the
>> > link:http://msdn2.microsoft.com/en-us/library/aa463113.aspx.
>> > After following all the steps & OS boot, how to invoke Application
>> > verifier
>> > to test "mydriver.dll"(a sample stream driver created for test)? this
>> > procedure is not clear.
>> > Also, why do i need tux.exe/device.exe in :set VERIFY_MODULES=tux.exe
>> > device.exe mydriver.dll ?
>>
>>
>>

Dear Marty,
I'm sorry that I forgot to mention that the "Verify.txt" is not getting
created in "Release" Directory.
I'll explain you the steps followed:
1.I tried to copy all necessary files using "getappverif_cetk.bat"
(WCETK\DDTK\DESKTOP\) ;but it didn't work.
2.I tried Getav.bat sample given in the blog but that too didn't work.
3.So I manually copied shim*.*,appverif*.*,etc to release folder.
4.Then I set environment variables from command prompt as follows:
set IMGSHIMENABLE=1
set VERIFY_MODULES=mydriver.dll
set VERIFY_SHIMS=shim_heap.dll
set VERIFY_OPTIONS=NoMapFiles EnableFanOut IgnoreNullFree

5.Then, I execute makeverifyfile.bat & get the following messages:
Setting shims to apply: shim_heap.dll
> > Setting verify options: NoMapFiles EnableFanOut IgnoreNullFree
> > Setting modules to verify: mydriver.dll
> > Done creating automatic shim file!
> > Renaming lmemdebug_autoshim to lmemdebug...

6.But when I check Release directory, no file named "Verify.txt" is created!!!
7.I do a "Build & Sysgen Current BSP" from PB & boot the device(currently,
just the emulator).
8.During boot time, shims are getting applied to all modules & not serving
the purpose of testing "mydriver.dll".

Regards,
Joseph




"Marty Larson" wrote:

> Hi, Joseph,
>
> The output of makeverifyfile.bat is a file named verify.txt. It sounds like
> that file isn't being opened and parsed correctly. Can you double-check that
> it's available in your release directory?
>
> --Marty Larson
>
> "joseph" <joseph@discussions.microsoft.com> wrote in message
> news:0F4B35AC-4E63-4970-B020-AA35D1D6C53D@microsoft.com...
> > Dear Marty,
> > Thanks a lot for the wonderful link.
> > I want to insert shims to "mydriver.dll".
> > But, I'm getting PB debug messages as follows during booting:
> > 1660 PID:83fa2b3a TID:83fa2b0a Shim autoloader: launching appverif.exe -m
> > {all} -s shim_heap.dll
> > 1810 PID:23f99aaa TID:23f99bb2 Shim autoloader: being loaded into app
> > verifier binary
> > 1820 PID:23f99aaa TID:23f99bb2 Loading shim 'shim_heap.dll'
> > 2050 PID:23f99aaa TID:23f99bb2 Shim_heap: Loaded into process
> > 'appverif.exe'
> > 2130 PID:23f99aaa TID:23f99bb2 Applying shim 'shim_heap.dll' to module
> > '{all}'
> > 2180 PID:23f99aaa TID:23f99bb2 Loading shim 'shim_verifier.dll'
> > 2290 PID:23f99aaa TID:23f99bb2 Applying shim 'shim_verifier.dll' to
> > module '{all}'
> > 2300 PID:23f99aaa TID:23f99bb2 Enabling shim engine...
> > 2410 PID:23f99aaa TID:23f99bb2 Verifier loader: SUCCESS
> >
> >
> > ---> Here, I expected "Applying shim 'shim_verifier.dll' to module
> > 'mydriver.dll'".But why it is applying for "{all}"?
> > When I run makeverifyfile.bat, it's giving following messages:
> > Setting shims to apply: shim_heap.dll
> > Setting verify options: NoMapFiles EnableFanOut IgnoreNullFree
> > Setting modules to verify: mydriver.dll
> > Done creating automatic shim file!
> > Renaming lmemdebug_autoshim to lmemdebug...
> >
> > which shall confirm that:set VERIFY_MODULES=mydriver.dll is properly
> > set.But, why it is happening for {all} modules during booting?
> >
> >
> > "Marty Larson" wrote:
> >
> >> Hi, Joseph,
> >>
> >> Here's a pretty comprehensive article on this subject that should guide
> >> you
> >> through this process:
> >> http://blogs.msdn.com/hopperx/archiv...-mobile-6.aspx
> >>
> >> --Marty Larson [MS]
> >>
> >> "joseph" <joseph@discussions.microsoft.com> wrote in message
> >> news:39038ED9-C061-40EC-8B7D-7C44BC7C5494@microsoft.com...
> >> > Hi All,
> >> > I've read the procedure to use application verifier to test drivers
> >> > from
> >> > the
> >> > link:http://msdn2.microsoft.com/en-us/library/aa463113.aspx.
> >> > After following all the steps & OS boot, how to invoke Application
> >> > verifier
> >> > to test "mydriver.dll"(a sample stream driver created for test)? this
> >> > procedure is not clear.
> >> > Also, why do i need tux.exe/device.exe in :set VERIFY_MODULES=tux.exe
> >> > device.exe mydriver.dll ?
> >>
> >>
> >>
>
>
>

Joseph,

The file will be created in %_flatreleasedir% - maybe that environment
variable wasn't set, so verify.txt ended up in the root directory?

--Marty Larson [MS]

"joseph" <joseph@discussions.microsoft.com> wrote in message
news:7F6D2744-B50B-4178-AB2B-05ACD70DE303@microsoft.com...
> Dear Marty,
> I'm sorry that I forgot to mention that the "Verify.txt" is not getting
> created in "Release" Directory.
> I'll explain you the steps followed:
> 1.I tried to copy all necessary files using "getappverif_cetk.bat"
> (WCETK\DDTK\DESKTOP\) ;but it didn't work.
> 2.I tried Getav.bat sample given in the blog but that too didn't work.
> 3.So I manually copied shim*.*,appverif*.*,etc to release folder.
> 4.Then I set environment variables from command prompt as follows:
> set IMGSHIMENABLE=1
> set VERIFY_MODULES=mydriver.dll
> set VERIFY_SHIMS=shim_heap.dll
> set VERIFY_OPTIONS=NoMapFiles EnableFanOut IgnoreNullFree
>
> 5.Then, I execute makeverifyfile.bat & get the following messages:
> Setting shims to apply: shim_heap.dll
>> > Setting verify options: NoMapFiles EnableFanOut IgnoreNullFree
>> > Setting modules to verify: mydriver.dll
>> > Done creating automatic shim file!
>> > Renaming lmemdebug_autoshim to lmemdebug...
>
> 6.But when I check Release directory, no file named "Verify.txt" is
> created!!!
> 7.I do a "Build & Sysgen Current BSP" from PB & boot the device(currently,
> just the emulator).
> 8.During boot time, shims are getting applied to all modules & not serving
> the purpose of testing "mydriver.dll".
>
> Regards,
> Joseph
>
>
>
>
> "Marty Larson" wrote:
>
>> Hi, Joseph,
>>
>> The output of makeverifyfile.bat is a file named verify.txt. It sounds
>> like
>> that file isn't being opened and parsed correctly. Can you double-check
>> that
>> it's available in your release directory?
>>
>> --Marty Larson
>>
>> "joseph" <joseph@discussions.microsoft.com> wrote in message
>> news:0F4B35AC-4E63-4970-B020-AA35D1D6C53D@microsoft.com...
>> > Dear Marty,
>> > Thanks a lot for the wonderful link.
>> > I want to insert shims to "mydriver.dll".
>> > But, I'm getting PB debug messages as follows during booting:
>> > 1660 PID:83fa2b3a TID:83fa2b0a Shim autoloader: launching
>> > appverif.exe -m
>> > {all} -s shim_heap.dll
>> > 1810 PID:23f99aaa TID:23f99bb2 Shim autoloader: being loaded into app
>> > verifier binary
>> > 1820 PID:23f99aaa TID:23f99bb2 Loading shim 'shim_heap.dll'
>> > 2050 PID:23f99aaa TID:23f99bb2 Shim_heap: Loaded into process
>> > 'appverif.exe'
>> > 2130 PID:23f99aaa TID:23f99bb2 Applying shim 'shim_heap.dll' to
>> > module
>> > '{all}'
>> > 2180 PID:23f99aaa TID:23f99bb2 Loading shim 'shim_verifier.dll'
>> > 2290 PID:23f99aaa TID:23f99bb2 Applying shim 'shim_verifier.dll' to
>> > module '{all}'
>> > 2300 PID:23f99aaa TID:23f99bb2 Enabling shim engine...
>> > 2410 PID:23f99aaa TID:23f99bb2 Verifier loader: SUCCESS
>> >
>> >
>> > ---> Here, I expected "Applying shim 'shim_verifier.dll' to module
>> > 'mydriver.dll'".But why it is applying for "{all}"?
>> > When I run makeverifyfile.bat, it's giving following messages:
>> > Setting shims to apply: shim_heap.dll
>> > Setting verify options: NoMapFiles EnableFanOut IgnoreNullFree
>> > Setting modules to verify: mydriver.dll
>> > Done creating automatic shim file!
>> > Renaming lmemdebug_autoshim to lmemdebug...
>> >
>> > which shall confirm that:set VERIFY_MODULES=mydriver.dll is properly
>> > set.But, why it is happening for {all} modules during booting?
>> >
>> >
>> > "Marty Larson" wrote:
>> >
>> >> Hi, Joseph,
>> >>
>> >> Here's a pretty comprehensive article on this subject that should
>> >> guide
>> >> you
>> >> through this process:
>> >> http://blogs.msdn.com/hopperx/archiv...-mobile-6.aspx
>> >>
>> >> --Marty Larson [MS]
>> >>
>> >> "joseph" <joseph@discussions.microsoft.com> wrote in message
>> >> news:39038ED9-C061-40EC-8B7D-7C44BC7C5494@microsoft.com...
>> >> > Hi All,
>> >> > I've read the procedure to use application verifier to test drivers
>> >> > from
>> >> > the
>> >> > link:http://msdn2.microsoft.com/en-us/library/aa463113.aspx.
>> >> > After following all the steps & OS boot, how to invoke Application
>> >> > verifier
>> >> > to test "mydriver.dll"(a sample stream driver created for test)?
>> >> > this
>> >> > procedure is not clear.
>> >> > Also, why do i need tux.exe/device.exe in :set
>> >> > VERIFY_MODULES=tux.exe
>> >> > device.exe mydriver.dll ?
>> >>
>> >>
>> >>
>>
>>
>>

Thanks Marty,

I changed the batch file & it's running as expected.

Thanks again for the very useful link to understand App.Verifier.

Regards,
Jo

"Marty Larson" wrote:

> Joseph,
>
> The file will be created in %_flatreleasedir% - maybe that environment
> variable wasn't set, so verify.txt ended up in the root directory?
>
> --Marty Larson [MS]
>
> "joseph" <joseph@discussions.microsoft.com> wrote in message
> news:7F6D2744-B50B-4178-AB2B-05ACD70DE303@microsoft.com...
> > Dear Marty,
> > I'm sorry that I forgot to mention that the "Verify.txt" is not getting
> > created in "Release" Directory.
> > I'll explain you the steps followed:
> > 1.I tried to copy all necessary files using "getappverif_cetk.bat"
> > (WCETK\DDTK\DESKTOP\) ;but it didn't work.
> > 2.I tried Getav.bat sample given in the blog but that too didn't work.
> > 3.So I manually copied shim*.*,appverif*.*,etc to release folder.
> > 4.Then I set environment variables from command prompt as follows:
> > set IMGSHIMENABLE=1
> > set VERIFY_MODULES=mydriver.dll
> > set VERIFY_SHIMS=shim_heap.dll
> > set VERIFY_OPTIONS=NoMapFiles EnableFanOut IgnoreNullFree
> >
> > 5.Then, I execute makeverifyfile.bat & get the following messages:
> > Setting shims to apply: shim_heap.dll
> >> > Setting verify options: NoMapFiles EnableFanOut IgnoreNullFree
> >> > Setting modules to verify: mydriver.dll
> >> > Done creating automatic shim file!
> >> > Renaming lmemdebug_autoshim to lmemdebug...
> >
> > 6.But when I check Release directory, no file named "Verify.txt" is
> > created!!!
> > 7.I do a "Build & Sysgen Current BSP" from PB & boot the device(currently,
> > just the emulator).
> > 8.During boot time, shims are getting applied to all modules & not serving
> > the purpose of testing "mydriver.dll".
> >
> > Regards,
> > Joseph
> >
> >
> >
> >
> > "Marty Larson" wrote:
> >
> >> Hi, Joseph,
> >>
> >> The output of makeverifyfile.bat is a file named verify.txt. It sounds
> >> like
> >> that file isn't being opened and parsed correctly. Can you double-check
> >> that
> >> it's available in your release directory?
> >>
> >> --Marty Larson
> >>
> >> "joseph" <joseph@discussions.microsoft.com> wrote in message
> >> news:0F4B35AC-4E63-4970-B020-AA35D1D6C53D@microsoft.com...
> >> > Dear Marty,
> >> > Thanks a lot for the wonderful link.
> >> > I want to insert shims to "mydriver.dll".
> >> > But, I'm getting PB debug messages as follows during booting:
> >> > 1660 PID:83fa2b3a TID:83fa2b0a Shim autoloader: launching
> >> > appverif.exe -m
> >> > {all} -s shim_heap.dll
> >> > 1810 PID:23f99aaa TID:23f99bb2 Shim autoloader: being loaded into app
> >> > verifier binary
> >> > 1820 PID:23f99aaa TID:23f99bb2 Loading shim 'shim_heap.dll'
> >> > 2050 PID:23f99aaa TID:23f99bb2 Shim_heap: Loaded into process
> >> > 'appverif.exe'
> >> > 2130 PID:23f99aaa TID:23f99bb2 Applying shim 'shim_heap.dll' to
> >> > module
> >> > '{all}'
> >> > 2180 PID:23f99aaa TID:23f99bb2 Loading shim 'shim_verifier.dll'
> >> > 2290 PID:23f99aaa TID:23f99bb2 Applying shim 'shim_verifier.dll' to
> >> > module '{all}'
> >> > 2300 PID:23f99aaa TID:23f99bb2 Enabling shim engine...
> >> > 2410 PID:23f99aaa TID:23f99bb2 Verifier loader: SUCCESS
> >> >
> >> >
> >> > ---> Here, I expected "Applying shim 'shim_verifier.dll' to module
> >> > 'mydriver.dll'".But why it is applying for "{all}"?
> >> > When I run makeverifyfile.bat, it's giving following messages:
> >> > Setting shims to apply: shim_heap.dll
> >> > Setting verify options: NoMapFiles EnableFanOut IgnoreNullFree
> >> > Setting modules to verify: mydriver.dll
> >> > Done creating automatic shim file!
> >> > Renaming lmemdebug_autoshim to lmemdebug...
> >> >
> >> > which shall confirm that:set VERIFY_MODULES=mydriver.dll is properly
> >> > set.But, why it is happening for {all} modules during booting?
> >> >
> >> >
> >> > "Marty Larson" wrote:
> >> >
> >> >> Hi, Joseph,
> >> >>
> >> >> Here's a pretty comprehensive article on this subject that should
> >> >> guide
> >> >> you
> >> >> through this process:
> >> >> http://blogs.msdn.com/hopperx/archiv...-mobile-6.aspx
> >> >>
> >> >> --Marty Larson [MS]
> >> >>
> >> >> "joseph" <joseph@discussions.microsoft.com> wrote in message
> >> >> news:39038ED9-C061-40EC-8B7D-7C44BC7C5494@microsoft.com...
> >> >> > Hi All,
> >> >> > I've read the procedure to use application verifier to test drivers
> >> >> > from
> >> >> > the
> >> >> > link:http://msdn2.microsoft.com/en-us/library/aa463113.aspx.
> >> >> > After following all the steps & OS boot, how to invoke Application
> >> >> > verifier
> >> >> > to test "mydriver.dll"(a sample stream driver created for test)?
> >> >> > this
> >> >> > procedure is not clear.
> >> >> > Also, why do i need tux.exe/device.exe in :set
> >> >> > VERIFY_MODULES=tux.exe
> >> >> > device.exe mydriver.dll ?
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>