>-----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: > >> On Mon, 28 Sep 2009, CLEMENT Francis wrote: >> >> > As said, ctrlclnt don't crash at all, at end of job >(action correctly >> > completed at xmail server side, and ctrlclnt output >correct and complete, >> > nothing missing), it seems to 'freeze' for about 30 >seconds (waiting for a >> > timeout ?) before ending then returns normally (no crash >dump, no drwatson, >> > no system event in logs, ...) but returns this 'strange' exit code. >> > >> > Same command from a workstation, do the same job, don't >freeze at all after >> > final output result, and return 0 >> > >> > I need to test older ctrlclnt versions to find last that >work 'localy' with >> > exit code 0 >> >> Looks like something triggered the debugger: >> >> http://www.ureader.com/message/1261932.aspx >> >> 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 _______________________________________________ xmail mailing list [email protected] http://xmailserver.org/mailman/listinfo/xmail
