>-----Message d'origine-----
>De : [email protected]
>[mailto:[email protected]]de la part de CLEMENT Francis
>Envoyé : mardi 29 septembre 2009 08:27
>À : 'XMail Users Mailing List'
>Objet : Re: [xmail] CtrlClnt local/remote diff in return value on w2k
>
>
>>-----Message d'origine-----
>>De : [email protected]
>>[mailto:[email protected]]de la part de Davide Libenzi
>>Envoyé : lundi 28 septembre 2009 19:37
>>À : XMail Users Mailing List
>>Objet : Re: [xmail] CtrlClnt local/remote diff in return value on w2k
>>
>>
>>On Mon, 28 Sep 2009, Davide Libenzi wrote:
>>
.....
>>> The error is DBG_TERMINATE_PROCESS.
>>> There are quite a few reports, if you google it.
>>
>>If you install WinDBG and you enable just in time debugging, 
>it should 
>>bring you right where the violation is.
>>Because, this is very likely an error triggered by CtrlClnt.
>>
>>
>>
>>- Davide
>>
>>
>
>Ok, I will try WinDBG and report asap
>
>Francis

Here is WinDBG result (some change in cmd line to mask sensitive data) :

CommandLine: C:\XMail\Bin\CtrlClnt.exe -s www.xxx.yyy.zzz -n 6017 -u
myusername -p mypassword userlist somehandleddomainname
Starting directory: C:\XMail\Bin
Symbol search path is:
SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
ModLoad: 00400000 0047e000   CtrlClnt.exe
ModLoad: 78460000 784e2000   ntdll.dll
ModLoad: 10000000 100fd000   C:\XMail\Bin\LIBEAY32.dll
ModLoad: 74fd0000 74fd9000   C:\WINNT\system32\WSOCK32.dll
ModLoad: 77e70000 77f2f000   C:\WINNT\system32\KERNEL32.DLL
ModLoad: 74fb0000 74fc4000   C:\WINNT\system32\WS2_32.DLL
ModLoad: 78000000 78045000   C:\WINNT\system32\MSVCRT.DLL
ModLoad: 78ed0000 78f35000   C:\WINNT\system32\ADVAPI32.DLL
ModLoad: 770c0000 7712f000   C:\WINNT\system32\RPCRT4.dll
ModLoad: 74fa0000 74fa8000   C:\WINNT\system32\WS2HELP.DLL
ModLoad: 77f40000 77f7d000   C:\WINNT\system32\GDI32.dll
ModLoad: 77e00000 77e5f000   C:\WINNT\system32\USER32.dll
ModLoad: 78130000 781cb000   C:\WINNT\system32\MSVCR80.dll
ModLoad: 00230000 00261000   C:\XMail\Bin\SSLEAY32.dll
(ad8.aac): Break instruction exception - code 80000003 (first chance)
eax=00000000 ebx=00131f04 ecx=00000000 edx=00132c48 esi=7ffdf000
edi=00131f78
eip=7847193c esp=0012f984 ebp=0012fc98 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:
7847193c cc              int     3
0:000> g
ModLoad: 74f50000 74f6d000   C:\WINNT\system32\msafd.dll
ModLoad: 74f90000 74f97000   C:\WINNT\System32\wshtcpip.dll
(ad8.888): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=00000000 ebx=00000000 ecx=0047a410 edx=00000ae4 esi=0047a400
edi=00000000
eip=7846f281 esp=00b2fba0 ebp=00b2fc00 iopl=0         nv up ei pl zr na pe
nc
cs=001b  ss=0023  ds=0023  es=0023  fs=0038  gs=0000
efl=00010246
ntdll!RtlpWaitForCriticalSection+0x8a:
7846f281 ff4010          inc     dword ptr [eax+10h]
ds:0023:00000010=????????

I'm not a windbg specialist ;) What do you mean with "enable just in time
debugging" ?
Should I do somethink more with Windbg at this point ? 

Francis
_______________________________________________
xmail mailing list
[email protected]
http://xmailserver.org/mailman/listinfo/xmail

Reply via email to