If this happens on Win2k or WinXP, I would heartily recommend trying to
debug this with WinDBG (which is available as a free download as part of
the Windows 2000 DDK, and part of MSDN in the Windows DDK).
Cheers,
/ h+
> -----Original Message-----
> From: gam...@li...
> [mailto:gam...@li...]On Behalf Of
> Javier Arevalo
> Sent: Thursday, August 29, 2002 3:17 AM
> To: GDWindows
> Subject: [GD-Windows] Process hanging inside ExitProcess()
>
>
> Hi!
>
> We currently have this annoying bug where, every few days, the game hangs
> when quitting, inside CRT's call to ExitProcess() with one (sometimes two)
> additional threads running. Of course, it only hangs in our retail builds,
> without our helpful debug logs. When we try to break into the debugger, it
> dumps the following message to the debug output:
>
> DBG: Break command failed within 3 seconds.
> DBG: Potential deadlock. Soft broken.
>
> The usual suspect is the multithreaded sound DLL, since the only reason
> ExitProcess() might hang seems to be while waiting for DLLs to detach. We
> use the undocumented MSVC++ 6 trick for assigning names to threads (cool!)
> so we can identify those in the debugger, but when we get this particular
> deadlock, MSVC++ seems to "forget" the names, and stack traces only show a
> couple levels inside KERNEL32, none of our user code. Thus we are not sure
> which DLLs and/or threads are causing this deadlock.
>
> Anybody has suggestions that can be helpful for debugging and/or solving
> this problem?
>
> Thanks in advance,
> Javier Arevalo
> Pyro Studios
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Gamedevlists-windows mailing list
> Gam...@li...
> https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows
> Archives:
> http://sourceforge.net/mailarchive/forum.php?forum_id=555
>
|