Hello, On 6/21/07, Jhorsh Muhammed <[EMAIL PROTECTED]> wrote: > Currently I have a problem, my application is not exit properly under > Windows Vista. All threads were stopped but process is not stopped. > If I didn't initialize SipX lib, application is closed successfully, > elsewhere I try to uninitialize library, application is not exit. > When I try to debug: Visual Studio reports me that the process appears to be > deadlocked and all threads have been stopped
Could you try update your sourcesand test again? I have recently commited a hack, which allow thread names to show in Visual Studio debugger. You'll see which thread is deadlocked then. However I guess it is OsSysLog thread, as it use _vsnprintf(). Strange thing is how one thread could be deadlocked? It looks like a bad bug in synchronization somewhere in the code. I know that OsSysLog have some problems with synchronization, but have no time to chase it down. So, patches are always welcome. -- Regards, Alexander Chemeris. SIPez LLC. SIP VoIP, IM and Presence Consulting http://www.SIPez.com tel: +1 (617) 273-4000 _______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
