dev_andy

Our VB6 app uses lots of windows controls and common controls.

When we close our application it breaks into debugger.

We even tried with a simple VB6 app by removing all the control'a and no code and the same behavior happens.

Here is the output from Windbg.


Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.

*** wait with pending attach
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
ModLoad: 00400000 00472000 D:\Anand\Temp_srcCode\Silica Vista\Source-Code\vb\SCard\SCard.exe
ModLoad: 7c900000 7c9b0000 C:\WINDOWS\system32\ntdll.dll
ModLoad: 5ad10000 5ad56000 C:\WINDOWS\System32\verifier.dll
ModLoad: 00360000 00380000 C:\WINDOWS\System32\vrfcore.dll
ModLoad: 00380000 003bd000 C:\WINDOWS\System32\vfbasics.dll
ModLoad: 7c800000 7c8f4000 C:\WINDOWS\system32\kernel32.dll
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 771ac000 C:\WINDOWS\system32\OLEAUT32.dll
ModLoad: 76390000 763ad000 C:\WINDOWS\system32\IMM32.DLL
ModLoad: 5ad70000 5ada8000 C:\WINDOWS\system32\uxtheme.dll
ModLoad: 74720000 7476b000 C:\WINDOWS\system32\MSCTF.dll
ModLoad: 755c0000 755ee000 C:\WINDOWS\system32\msctfime.ime
ModLoad: 77fe0000 77ff1000 C:\WINDOWS\system32\Secur32.dll
ModLoad: 71ab0000 71ac7000 C:\WINDOWS\system32\WS2_32.dll
ModLoad: 71aa0000 71aa8000 C:\WINDOWS\system32\WS2HELP.dll
ModLoad: 77c00000 77c08000 C:\WINDOWS\system32\VERSION.DLL
ModLoad: 605d0000 605d9000 C:\WINDOWS\system32\mslbui.dll
ModLoad: 77f60000 77fd6000 C:\WINDOWS\system32\SHLWAPI.dll
ModLoad: 5d090000 5d127000 C:\WINDOWS\system32\COMCTL32.dll
ModLoad: 773d0000 774d2000 C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2180_x-ww_a84f1ff9\comctl32.dll
Break-in sent, waiting 30 seconds...
WARNING: Break-in timed out, suspending.
This is usually caused by another thread holding the loader lock
(cc4.410): Wake debugger - code 80000007 (first chance)
eax=04580000 ebx=0012efb4 ecx=00001000 edx=7c90eb94 esi=000005d8 edi=00000000
eip=7c90eb94 esp=0012ef78 ebp=0012ef98 iopl=0 nv up ei pl zr na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\WINDOWS\system32\ntdll.dll -
ntdll!KiFastSystemCallRet:
7c90eb94 c3 ret

Can anyone help

thanks





Re: Application Compatibility for Windows Vista Test Case31 application breaks into debugger

Bruce N. Baker - MSFT

Can you remove references to comctrl32.dll




Re: Application Compatibility for Windows Vista Test Case31 application breaks into debugger

Bruce N. Baker - MSFT

Check out this thread also.

http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=1404212&SiteID=1






Re: Application Compatibility for Windows Vista Test Case31 application breaks into debugger

dev_andy

I removed references to comctl32.dll and all other OCX, still it was breaking into debugger. Then i've observed that the problem could be with the borland dll's that we 've developed which our VB exe's use. i thought as these dll's are multithreaded it is breaking into debugger. So i compiled them as single threaded dll.

Still it breaks into debugger saying "Unloading DLL containing an active critical section."

also we are not unloading dll while closing VB exe.

following is the dump from win debugger

Executable search path is:
ModLoad: 00400000 00473000 D:\Anand\Temp_srcCode\Silica Vista\Source-Code\vb\SCard\SCard.exe
ModLoad: 7c900000 7c9b0000 C:\WINDOWS\system32\ntdll.dll
ModLoad: 5ad10000 5ad56000 C:\WINDOWS\System32\verifier.dll
ModLoad: 00360000 00380000 C:\WINDOWS\System32\vrfcore.dll
ModLoad: 00380000 003bd000 C:\WINDOWS\System32\vfbasics.dll
ModLoad: 7c800000 7c8f4000 C:\WINDOWS\system32\kernel32.dll
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 771ac000 C:\WINDOWS\system32\OLEAUT32.dll
ModLoad: 76390000 763ad000 C:\WINDOWS\system32\IMM32.DLL
ModLoad: 5ad70000 5ada8000 C:\WINDOWS\system32\uxtheme.dll
ModLoad: 74720000 7476b000 C:\WINDOWS\system32\MSCTF.dll
ModLoad: 755c0000 755ee000 C:\WINDOWS\system32\msctfime.ime
ModLoad: 77fe0000 77ff1000 C:\WINDOWS\system32\Secur32.dll
ModLoad: 71ab0000 71ac7000 C:\WINDOWS\system32\WS2_32.dll
ModLoad: 71aa0000 71aa8000 C:\WINDOWS\system32\WS2HELP.dll
ModLoad: 77c00000 77c08000 C:\WINDOWS\system32\VERSION.DLL
ModLoad: 605d0000 605d9000 C:\WINDOWS\system32\mslbui.dll
Break-in sent, waiting 30 seconds...
WARNING: Break-in timed out, suspending.
This is usually caused by another thread holding the loader lock
(238.f9c): Wake debugger - code 80000007 (first chance)
eax=042b0000 ebx=0012ef90 ecx=00001000 edx=7c90eb94 esi=00000490 edi=00000000
eip=7c90eb94 esp=0012ef54 ebp=0012ef74 iopl=0 nv up ei pl zr na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\WINDOWS\system32\ntdll.dll -
ntdll!KiFastSystemCallRet:
7c90eb94 c3 ret
0:000> g


=======================================
VERIFIER STOP 00000201 : pid 0x238: Unloading DLL containing an active critical section.

03AA0460 : Critical section address.
00000000 : Critical section initialization stack trace.
014E0FE8 : DLL name address.
03A30000 : DLL base address.

Can someone help

Thanks






Re: Application Compatibility for Windows Vista Test Case31 application breaks into debugger

Bruce N. Baker - MSFT

A quick take is that it sounds like you might need to contact Borland.




Re: Application Compatibility for Windows Vista Test Case31 application breaks into debugger

dev_andy

hi,

is there anyway to get around the dll unloading probliem & breaking into debugger. we r still stuck at this point

thanks






Re: Application Compatibility for Windows Vista Test Case31 application breaks into debugger

Bruce N. Baker - MSFT

Lets back up a bit. Are you running into the same problem with a simple VB6 application with no controls