Visual Studio Application Verifier Forum

AppVerifier(64) breakpoints, exceptions and empty logs?

Mon, 12 Oct 2009 15:47:22 Z

Hi,
I think this is the correct place to post this, as I cant find Visual Studio Team System Forums->Visual Studio Application Verifier
in the dialog.
I'm looking into a problem with my app running under AppVerifier.
I have Vista Ultimate 64bit OS, a 32bit application I wish to test, and a 64 bit version of AppVerifier.
I tag the app in the verifier, and set the tests I want to perform (Basics).
Run WinDbg, click File->OpenExecutable and run the .exe.
I immediately hit this breakpoint:

ModLoad: 00000000`00400000 00000000`00aee000   App1_Release.exe
ModLoad: 00000000`77c10000 00000000`77d90000   ntdll.dll
ModLoad: 00000000`77db0000 00000000`77f10000   ntdll32.dll
ModLoad: 00000000`75cb0000 00000000`75cf5000   C:\Windows\system32\wow64.dll
ModLoad: 00000000`75c60000 00000000`75cae000   C:\Windows\system32\wow64win.dll
ModLoad: 00000000`75c50000 00000000`75c59000   C:\Windows\system32\wow64cpu.dll
(1184.9c0): Break instruction exception - code 80000003 (first chance)
ntdll!DbgBreakPoint:
00000000`77c54ea0 cc              int     3

& later on in the run :

ModLoad: 00000000`76600000 00000000`76607000   C:\Windows\syswow64\PSAPI.DLL
(1210.814): WOW64 breakpoint - code 4000001f (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
ntdll32!DbgBreakPoint:
77dc0004 cc              int     3

These 2 happen with or without the AppVerifiers modifications, It would be nice to know what they are about, I'm not sure its essential.
I can hit F5 to continue, the app runs, constantly hitting :

ModLoad: 76860000 76869000   C:\Windows\syswow64\LPK.DLL
(127c.a58): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
ntdll!RtlVirtualUnwind+0x215:
00000000`77c5b745 488b02          mov     rax,qword ptr [rdx] ds:fffffa60`10999b70=????????????????

and so it continues.
The main loop of the app runs uninterrupted, but then starts throwing these exceptions again on exit:

(127c.a58): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
ntdll!RtlVirtualUnwind+0x215:
00000000`77c5b745 488b02          mov     rax,qword ptr [rdx] ds:fffffa60`10999ab8=????????????????

about 20 times.

Despite all this my Appverifier never seems to generate any more detailed a log than this:

<? xml version="1.0" encoding="UTF-8" standalone="no" ?>

- < avrf:logfile xmlns:avrf =" Application Verifier " >

< avrf:logSession TimeStarted =" 2009-10-12 : 14:25:28 " PID =" 5216 " Version =" 2 " />

</ avrf:logfile >

any help would be appreciated,

Cheers
Bree

Forum Migration is Complete!

Thu, 09 Oct 2008 00:50:53 Z

The Forum Migration is complete and this forum has successfully been migrated. New Forum is located here:
http://social.msdn.microsoft.com/Forums/en-US/vstsappverifier/threads/

Thanks!

This forum has moved the Week of October 6th, 2008

Fri, 03 Oct 2008 06:27:00 Z

Microsoft has created a new forums platform (MSDN | TechNet | Expression | Microsoft) with increased performance, stability, and an improved user experience. During the week of October 6, 2008 this forum will be moving to the new platform. To make sure this is a smooth transition, we want everyone using this forum to have a chance to try out the new forums in advance, and give feedback. We’ve created a Sandbox forum, where you can create threads and try out functionality, and a suggestions forum where you can give us your feedback. Please take some time to go to the new forums today and let us know what you think.

On the day the forum moves to the new platform, a post will be made letting you know the process has been started, and the forum will be locked to new posts. Once the process is complete, a final post to the forum will be made letting you know the forum has moved.

1. All posts in the forum will be preserved

2. Any points you’ve received for replies will move with you (on a per forum basis)

3. Any bookmarks to this forum or threads within this forum will redirect to their new location

4. Your “My Threads” will be preserved on the new platform

The only thing you’ll need to do after migration is set Windows Live Alerts for any threads you were tracking.

If you have feedback, let us know in the suggestions forum

Thanks!

Alicia

CreateProcess Application Verifier bug

Fri, 26 Sep 2008 13:46:35 Z

Hi,

I think this is similar to one of the recent post.

For CreateProcess, MSDN says "If the executable module is a 16-bit application, lpApplicationName should be NULL".
But Application Verifier complains if CreateProcess's first param (i.e. lpApplicationName) is NULL.

Is it a known issue with App Verifier. Should this be added into the Extra list of the Application Verfier?

If not, how to solve this (because App Verifier is complaining when I invoke 16 bit app)?

Please help me to solve this problem.

Thanks,

Vikas.

CreateProcess for 16 bit applications failes for Application Verifier

Thu, 25 Sep 2008 08:30:04 Z

Hi,

I have a problem testing my mfc application while using Application Verifier.

I have used "CreateProcess" API. Where first parameter is given NULL because the application I want to execute is a 16 bit app.

Please go through the following statements.....

Object Squatting Vulnerability:

Any application that launches other processes may potentially open itself up to squatting attacks.

The most common ways to do this are:
Passing a NULL lpApplicationName to CreateProcess
Passing a command line to CreateProcess (or similar API) that contains unquoted spaces in the program portion.

For example, this command line: C:\program files\foo.exe –t –g C:\program files\foo\bar would be flagged as invalid by SecurityChecks

Visit: http://technet.microsoft.com/en-us/library/cc700837.aspx

If I use 1st param as NULL & second using 32 bit application along
with some command line atttributes then it works fine.

So now how to pass my application through Application Verifier which
uses CreateProcess for 16 bit applications.?

Thanx & Regards,

Vinod.

Can't find how to disable the application verifier

Wed, 03 Sep 2008 08:13:38 Z

Hi,

I'd like to disable the Application Verifier in Visual Studio C++ 2008 but, can't find how to do it.

I want to do this because it seems the compiler is not inlining the functions I forced to inline, so I've searched and found this (http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=99022), so I want to disable the application verifier.

I went to Project, Properties, and selected "Disable" for the three fields, Heap Verification, Handle Verification and Locks Verification, selected Apply, but still it seems that it's not inlining my functions.

Even tried to create a new project, and the three fields are already not disabled, so I run again into the same problem.

Any idea?

TIA & Regards ...

Visual Studio 2008 and the .NET Framework 3.5 SP1 Now Available!

Wed, 13 Aug 2008 21:20:18 Z

We are very happy to announce immediate availability on the Microsoft Download Center of Service Pack 1 for Visual Studio 2008 and the .NET Framework 3.5. You can find the download here.

Question about the standalone version of Application Verifier?

Fri, 27 Apr 2007 20:35:02 Z

If you have a question about the standalone Application Verifier for Windows tool that does not ship with Visual Studio, you should head over to microsoft.public.win32.programmer.tools newsgroup. The standalone application verifier has been updated and contains new rules not available in the Visual StudioTeam Developer and Team Suite version. It is available from: Application Verifier Download

If you have a question about the standalone Application Verifier for Windows CE tool that does not ship with Visual Studio, you should head over to microsoft.public.windowsCE.testtools newsgroup.

This forum is for questions only about the Application Verifier feature that ships with Visual Studio Team Developer and Visual Studio Team Suite.

WM Emulator & Windows CE Test Kit

Sat, 19 Jul 2008 06:32:27 Z

Hi,

Attempting to run Application Verifier in Windows CE Test Kit, however having some difficulty connecting CETK to Emulator. I've tested the connection of the CETK to Emulator under the Device Properties when configuring the Platform Manager and everything appears to be ok at that point. However, when I set to connect by clicking on the Connection button under the Device Properties, the Emulator is not listed under the Kit Server.

I'm using the following tools:

- WM 5.0 MSFP Emulator Images: Pocket PC Emulator, Emulator Device Mgr. to Cradle

- WM Device Center (ActiveSync for Vista - Home Premium)

- Windows CE 5.0 Test Kit

- Application Verifier for WM 5.0

- Vista Home Premium

any help is appreciated

Question about virtual memory when using application verifier

Tue, 15 Jul 2008 03:33:03 Z

Dear All

When I use application verifier to test my application. I found it will throw exception and failed. This exception is from _beginthreadex or new operation. And I get API to print memory information. I found my applicaiton will use more phy-memory and virtual memory than before when I laungh appverifier.

And still I found the unusal memory situation. The virtual memory will be occupied to leave only 17-18MB (without appVerifier it will leave almost 500-1000MB,) I really don't know why it uses so much virtual memory and doesn't free them.

Please help me about this question, why it uses more virtual memory and phy-memory when launching appVerifier than without appverifier. And how I can fix this problem. Thanks a lot.

Application Verifier for WM + jar file

Fri, 11 Jul 2008 01:42:41 Z

hello,

Wondering if the Application Verifier for Windows Mobile can be used to track jar files running on a Pocket PC?

any help is appreciated.

jim

APPLICATION_VERIFIER_LOCK_IN_FREED_HEAP

Mon, 02 Jun 2008 19:31:33 Z

How do i fix this problem during shutdown with a freeing an active critical section in the msxml code? the trace when this happens is this:

ChildEBP RetAddr
0012b1b4 6e923760 ntdll!DbgBreakPoint
0012b3b8 6c7730ee vrfcore!VerifierStopMessageEx+0x4b5
0012b3dc 6c765fa9 vfbasics!VfBasicsStopMessage+0x8e
0012b424 6c769cc9 vfbasics!AVrfpFreeMemLockChecks+0x109
0012b440 6c76bd86 vfbasics!AVrfpFreeMemNotify+0x39
0012b458 773f168d vfbasics!AVrfpNtdllHeapFreeCallback+0x16
0012b474 6e877e97 ntdll!AVrfInternalHeapFreeNotification+0x4d
0012b4c8 773dafe1 verifier!AVrfDebugPageHeapDestroy+0x137
0012b4dc 7637098e ntdll!RtlDestroyHeap+0x7a
0012b4e8 6c76be6d kernel32!HeapDestroy+0xe
0012b4f8 71f9b30a vfbasics!AVrfpHeapDestroy+0x2d
0012b508 71f9b2da msxml3!heap_destroy+0x1f
0012b514 71f9b297 msxml3!_MP_HEAP_ENTRY::~_MP_HEAP_ENTRY+0x1c
0012b528 71f9aa2a msxml3!MpHeapDestroy+0x53
0012b530 71f9ae5d msxml3!MpHeapExit+0x18
0012b534 71f9ae49 msxml3!Memory_exit+0xa
0012b540 6e8759c9 msxml3!InitDllMain+0x104
0012b588 6e927fcb verifier!AVrfpStandardDllEntryPointRoutine+0x109
0012b5d0 6c77118e vrfcore!VfCoreStandardDllEntryPointRoutine+0x127
0012b628 7739e1c4 vfbasics!AVrfpStandardDllEntryPointRoutine+0x10e

the initialization stack trace is here:

0047911c 7739cf8f ntdll!RtlInitializeCriticalSectionAndSpinCount+0x19
00479120 6c766885 vfbasics!AVrfpInitializeCriticalSectionCommon+0x135
00479124 6c766a02 vfbasics!AVrfpRtlInitializeCriticalSection+0x12
00479128 71f68dc9 msxml3!SafeInitializeCriticalSection+0x38
0047912c 71f68da0 msxml3!X_CRITICAL_SECTION::Initialize+0x12
00479130 71f7ba40 msxml3!NodeManager::New+0x5e
00479134 71f6fd92 msxml3!Document::init+0x52
00479138 71f6faee msxml3!_createDOMDocument+0x19
0047913c 71fa608c msxml3!CreateDOMDocument+0x3a
00479140 71f69b31 msxml3!ClassFactory_CreateInstance+0x50
00479144 7672750f ole32!CServerContextActivator::CreateInstance+0x172
00479148 7672705b ole32!ActivationPropertiesIn:elegateCreateInstance+0x108
0047914c 7672772d ole32!CApartmentActivator::CreateInstance+0x112
00479150 7672764f ole32!CProcessActivator::CCICallback+0x6d
00479154 76727609 ole32!CProcessActivator::AttemptActivation+0x2c
00479158 767275ba ole32!CProcessActivator::ActivateByContext+0x4f
0047915c 767276af ole32!CProcessActivator::CreateInstance+0x49
00479160 7672705b ole32!ActivationPropertiesIn:elegateCreateInstance+0x108
00479164 76727121 ole32!CClientContextActivator::CreateInstance+0xb0
00479168 7672705b ole32!ActivationPropertiesIn:elegateCreateInstance+0x108
0047916c 767272c5 ole32!ICoCreateInstanceEx+0x403
00479170 7674e2a2 ole32!CComActivator:oCreateInstance+0xd9
00479174 7674e203 ole32!CoCreateInstanceEx+0x38
00479178 7674e1bc ole32!CoCreateInstance+0x37
0047917c 00422bb3 NetSP!ATL::CComPtrBase<MSXML2::IXMLDOMDocument>::CoCreateInstance+0x73 [c:\program files\microsoft visual studio 8\vc\atlmfc\include\atlcomcli.h @ 234]
00479180 0041f70b NetSP!WinMail_Get_AttributeValue+0x7b [c:\v7\current\netsp\windowsmailset.cpp @ 276]
00479184 0041fb5a NetSP!WinMail_Get_NewsAccountFilename+0x10a [c:\v7\current\netsp\windowsmailset.cpp @ 312]
00479188 00417928 NetSP!WinMain+0xa98 [c:\v7\current\netsp\netsp.cpp @ 752]
0047918c 004289f6 NetSP!__tmainCRTStartup+0x286 [f:\sp\vctools\crt_bld\self_x86\crt\src\crtexe.c @ 589]

Thanks

Application Verifier with Unit Test projects

Mon, 26 Feb 2007 15:24:59 Z

I find the Application Verfifer a very useful tool. I also like the Unit Testing support that comes with Visual Studio 2005 so we write our tests using managed C++ which calls our unmanaged C++ code which is built as a static library.

However, we can't find a way of running a Unit Test through the Application Verifier in the VS 2005 IDE. Is this possible ? We resort to doing it outside of the IDE by using the standalone version 3.3 of Application Verifier to instrument mstest.exe itself and then run the Unit Tests from the command line i.e.

C:\Program Files\Microsoft Visual Studio 8\VC>mstest /testcontainer:"\TestProject1.dll" /noisolation

Is there another way ?

Using the Standalone Appication Verifier with Web Applications

Tue, 11 Dec 2007 22:52:23 Z

Hi,

I've recently downloaded the Application Verifier 3.4 standalone program to test our Web Application for Heaps, Locks and Handles. The first step is to add an application to monitor. Since it is a Web Application, I do not have any particular .exe or dlls that I can add. After some searching on the Web I found some documentation that leads me to believe I should add the following:

aspnet_wp.exe

dllhost.exe

svchost.exe

inetinfo.exe

Two questions:

First question, since we are running our Web Application under IIS 6.0 is monitoring the aspnet_wp.exe going to do anything for me? Or should I be monitoring the w3wp.exe instead?

Second question, it seems as though with the dllhost.exe (or at least I think this is the one that is causing it) in the list if I browse to our Web Application, perform a few tasks, leave it (without logging out), then go back about 15 minutes later, I get a cannot find server error message. I then have to restart IIS in order for the site to be available again. In the Web Server event viewer I'm getting the following error message:

A process serving application pool 'Stage3AppPool' exceeded time limits during start up. The process id was '6048'.

Stage3AppPool is the application pool that has been assigned to this particular Web Application (with Application Verifier turned off, I do not get the error shown above). Application Verifier documentation indicates that it will slow down the Web Application Response time, due to the testing overhead. Can anyone point me in the right direction with regards to how to stop the Application Pool ('Stage3AppPool') from timing out while monitoring the exe's listed above?

Thanks, Calvin

Application verifier tool

Sun, 10 Sep 2006 16:12:07 Z

I want to use a good memory leakage tool for windows mobile 5.0. I found a tool Application verifier for windows mobile 5.0. I installed this tool and platform builder. But when I try to connect it only shows CE default device. Its not showing windows mobile devices. I found out the document with this tool. But not getting how to use this tool with visual studio. Please let me know if anybody use this tool or there is another tool for finding the memory leakage on windows mobile 5.0 device as well as emulator.

thnx n regards

Application Verifier problem, Unknown results

Fri, 01 Jun 2007 17:47:06 Z

I have an .dll I am trying to run the Application Verifier on a Windows Mobile 5 device. I have placed the .map and .cod files in the Windows directory on the device. After running, the results from the Application Verifier contains UNKNOWN. How can I get rid of the unknown results.

Application Verifier Tool for Windows Mobile 6.0

Mon, 03 Dec 2007 15:01:14 Z

Hi all,

is there an Application Verifier Tool for Windows Mobile 6.0 like for Windows Mobile 5.0, and where it can be downloaded? Now I am trying to test applicaion written for Windows Mobile 6.0 with Windows Embedded CE 6.0 Test Kit, but is doesn't work.

Thanks,

Lara

SHGetPathFromIDList crashes at Application Verifier...

Mon, 17 Sep 2007 05:24:13 Z

Dear All,

I have used SHBrowseForFolder in my application. I have handled BrowseCallbackProc. So when selection changes I have used SHGetPathFromIDList, but it fails at Nokia phone browser with Application Verifier. But without AV it erturns the path as : ::{20D04FE0-3AEA-1069-A2D8-08002B30309D}\::{416651E4-9C3C-11D9-8BDE-F66BAD1E3F3A}. So does anybody knows the reason for it & how to pass it through Application Verifier.

Thanx & Regards,

Vinod.

Application Verifier fails to initialize on Windows XP x64

Fri, 27 Apr 2007 11:31:13 Z

Hi,

hope this is the right newsgroup for my question. If not, my apologies.

I just installed the 64-bit standalone version of Application Verifier (v3.3, for x64 CPUs) on my system which runs Windows XP x64. I'm now trying to use it with a 64-bit application, but can't get Application Verifier to log anything.

When I run my executable in the debugger, I see the following messages:

AVRF: foo.exe: pid 0x1498: flags 0x80000000: application verifier enabled
'foo.exe': Loaded 'C:\WINDOWS\system32\verifier.dll', Exports loaded.
AVRF: failed to initialize verifier logging (C000003A).
AVRF: verifier.dll provider initialized for foo.exe with flags 0x80000000

The application starts up just fine - but there are no log files and no test results afterwards.

I found an old posting in a newsgroup where somebody was trying to use the 64-bit version of Application Verifier with a 32-bit app, and also failed to get any logs. However, in my case, both the Verifier and the app are 64-bit.

Thanks for any help or pointers!

Claus

Visual Studio Team System 2005 Application Verifier FAQ

Thu, 20 Apr 2006 19:59:04 Z

Here is a FAQ provided by the Application Verifier team to answers some of the most common questions about the Application Verifier tool that is included with Visual Studio Team Suite and Team Developer Editions.

Q: What is Application Verifier?

A: Application Verifier is a runtime verification tool used to find bugs in Windows applications. Application Verifier is supported only for native (unmanaged) code. Since it is a runtime tool, the application code needs to be exercised in order to be verified. Good test coverage is therefore essential.

Q: How can I get Application Verifier?

A: There are two versions of Application Verifier:

- A stand alone version that can be downloaded from http://www.microsoft.com/downloads/details.aspx?FamilyID=bd02c19c-1250-433c-8c1b-2619bd93b3a2&DisplayLang=en

- The integrated Application Verifier included in the Visual Studio Team Suite and Visual Studio Team System for Developers versions of Visual Studio 2005.

Q: What are the differences between the standalone version and the integrated version?

A: The major differences are:

- Only a subset of the checks available in the standalone version is available in the integrated version. Heaps, Handles and Locks checks are available in Visual Stdio.

- With the standalone version, the user needs to enable verifier settings using the tool and then launch his application. The verifier settings persist until the user deletes them using the tool. With the integrated version, verifier settings can be altered in the project property pages. These settings are applicable only when the user chooses to debug the application using Application Verifier by clicking on Debug->Start With Application Verifier.

Q: How do I launch my app using Application Verifier in Visual Studio?

A: Open your VC++ project in Visual Studio. Go to project properties and select "Application Verifier," enable desired settings or leave them at their default settings (all the checks are enabled by default). Click on Debug->Start With Application Verifier to start debugging with application verifier enabled.

Q: Why do I get the following message when I click on Debug->Start With Application Verifier?

""Access denied. You need administrative credentials to enable instrumentation settings on the selected executable image <<Image_Name>> on machine <<Machine_Name>>. Contact your system administrator for assistance"

A: You need administrative credentials to use Application Verifier

Q: What Operating Systems support Application Verifier?

A: Application Verifier is supported on Windows XP and Windows 2003. The following message is displayed on Windows 2000 when the integrated Application Verifier is used: "Application Verifier is not supported on the Operating System running on your machine <<Machine_Name>>. Please upgrade to Windows XP or above"

Q: Why am I getting the following message?

"Application Verifier requires an updated system file that is not detected on your machine <<Machine_Name>>. Do you want to go to the Windows download center to get the update?"

A: Your current Operating System requires an update in order to use Application Verifier. Clicking on OK will take you to the Microsoft download center where you can get the update.

Q: What kinds of errors are caught by the integrated Application Verifier in VS?

A: The integrated Application Verifier catches heap, handle and lock errors in native win32 applications. The most common of these are memory corruptions, which are very hard to troubleshoot. It catches invalid handle usage and invalid critical section usage as well. Application Verifier makes these difficult debugging problems easier to solve.

Q: Where can I find more information on Application Verifier?

A: MSDN has great documentation on both the standalone and the integrated Application Verifier.