Marcia
2007-12-04 19:26:02 UTC
Hello,
Another first-time user of AppVerifier and WinDbg here --
We are prepping our application for the VeriTest competency test and right
now have everything under "Basics" checked in AppVerifier. This is a VB6 app
that performs without error when run outside AppVerifier. We get no errors
when running under AppVerifier until we close the application, at which point
we get 2 Breakpoint exceptions. When run in WinDbg, we get several more
exceptions, some at the start of the app execution and some at the end. I
cannot determine at this point if this is an issue with our code or with VB6
(or something else altogether). I would like to start by showing you what
happens in WinDbg when the application opens. It appears we reach a
breakpoint even before all of the modules are loaded. Here it is:
Closing open log file c:\MyAppdevelopment\MyApp\DebugLogs\20071121_1018.log
Opened log file 'c:\MyAppdevelopment\MyApp\debuglogs\log_1103.txt'
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.
CommandLine: C:\MyAppdevelopment\MyApp\MyApp.exe
Symbol search path is:
SRV*c:\symbols*http://msdl.microsoft.com/download/symbols;symsrv*symsrv.dll*C:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
ModLoad: 00400000 004d5000 MyApp.exe
ModLoad: 7c900000 7c9b0000 ntdll.dll
AVRF: MyApp.exe: pid 0x1630: flags 0x80000181: application verifier enabled
ModLoad: 5ad10000 5ad56000 C:\WINDOWS\System32\verifier.dll
ModLoad: 00360000 00388000 C:\WINDOWS\System32\vrfcore.dll
ModLoad: 00390000 003c9000 C:\WINDOWS\System32\vfbasics.dll
ModLoad: 7c800000 7c8f5000 C:\WINDOWS\system32\kernel32.dll
AVRF: verifier.dll provider initialized for MyApp.exe with flags 0x80000181
ModLoad: 73420000 73574000 C:\WINDOWS\system32\MSVBVM60.DLL
ModLoad: 7e410000 7e4a0000 C:\WINDOWS\system32\USER32.dll
ModLoad: 77f10000 77f57000 C:\WINDOWS\system32\GDI32.dll
ModLoad: 77dd0000 77e6b000 C:\WINDOWS\system32\ADVAPI32.dll
ModLoad: 77e70000 77f01000 C:\WINDOWS\system32\RPCRT4.dll
ModLoad: 774e0000 7761d000 C:\WINDOWS\system32\ole32.dll
ModLoad: 77c10000 77c68000 C:\WINDOWS\system32\msvcrt.dll
ModLoad: 77120000 771ab000 C:\WINDOWS\system32\OLEAUT32.dll
(1630.1528): Break instruction exception - code 80000003 (first chance)
eax=014e6fec ebx=7ffdf000 ecx=00000001 edx=00000002 esi=014eafb0 edi=014e6fec
eip=7c901230 esp=0012fb20 ebp=0012fc94 iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000202
ntdll!DbgBreakPoint:
7c901230 cc int 3
When I hit "g", it loads the rest of the modules. Is the above a breakpoint
coming from ntdll, or is that simply the module that reports errors? I'm
sorry if this is a dumb question, but as a VB developer, you might imagine I
am quite lost looking at all of this "inside stuff" that I thought was being
handled by the runtime.
Any insight would be most appreciated!
Thanks,
Marcia
Another first-time user of AppVerifier and WinDbg here --
We are prepping our application for the VeriTest competency test and right
now have everything under "Basics" checked in AppVerifier. This is a VB6 app
that performs without error when run outside AppVerifier. We get no errors
when running under AppVerifier until we close the application, at which point
we get 2 Breakpoint exceptions. When run in WinDbg, we get several more
exceptions, some at the start of the app execution and some at the end. I
cannot determine at this point if this is an issue with our code or with VB6
(or something else altogether). I would like to start by showing you what
happens in WinDbg when the application opens. It appears we reach a
breakpoint even before all of the modules are loaded. Here it is:
Closing open log file c:\MyAppdevelopment\MyApp\DebugLogs\20071121_1018.log
Opened log file 'c:\MyAppdevelopment\MyApp\debuglogs\log_1103.txt'
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.
CommandLine: C:\MyAppdevelopment\MyApp\MyApp.exe
Symbol search path is:
SRV*c:\symbols*http://msdl.microsoft.com/download/symbols;symsrv*symsrv.dll*C:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
ModLoad: 00400000 004d5000 MyApp.exe
ModLoad: 7c900000 7c9b0000 ntdll.dll
AVRF: MyApp.exe: pid 0x1630: flags 0x80000181: application verifier enabled
ModLoad: 5ad10000 5ad56000 C:\WINDOWS\System32\verifier.dll
ModLoad: 00360000 00388000 C:\WINDOWS\System32\vrfcore.dll
ModLoad: 00390000 003c9000 C:\WINDOWS\System32\vfbasics.dll
ModLoad: 7c800000 7c8f5000 C:\WINDOWS\system32\kernel32.dll
AVRF: verifier.dll provider initialized for MyApp.exe with flags 0x80000181
ModLoad: 73420000 73574000 C:\WINDOWS\system32\MSVBVM60.DLL
ModLoad: 7e410000 7e4a0000 C:\WINDOWS\system32\USER32.dll
ModLoad: 77f10000 77f57000 C:\WINDOWS\system32\GDI32.dll
ModLoad: 77dd0000 77e6b000 C:\WINDOWS\system32\ADVAPI32.dll
ModLoad: 77e70000 77f01000 C:\WINDOWS\system32\RPCRT4.dll
ModLoad: 774e0000 7761d000 C:\WINDOWS\system32\ole32.dll
ModLoad: 77c10000 77c68000 C:\WINDOWS\system32\msvcrt.dll
ModLoad: 77120000 771ab000 C:\WINDOWS\system32\OLEAUT32.dll
(1630.1528): Break instruction exception - code 80000003 (first chance)
eax=014e6fec ebx=7ffdf000 ecx=00000001 edx=00000002 esi=014eafb0 edi=014e6fec
eip=7c901230 esp=0012fb20 ebp=0012fc94 iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000202
ntdll!DbgBreakPoint:
7c901230 cc int 3
When I hit "g", it loads the rest of the modules. Is the above a breakpoint
coming from ntdll, or is that simply the module that reports errors? I'm
sorry if this is a dumb question, but as a VB developer, you might imagine I
am quite lost looking at all of this "inside stuff" that I thought was being
handled by the runtime.
Any insight would be most appreciated!
Thanks,
Marcia