Re: problem with CMtex and CSingle lock - WAIT_ABANDONED
I suggest you convert your code to ATL::CMutex. It doesn't try to be too
MUCH abstract and doesn't carry that CObject crap with it.
WinDbg debugger can provide you with more information, especially in remote
mode. If you set a breakpoint at WAIT_ABANDONED return value, and inspect
the mutex object (in kernel mode), you can find which thread was holding it.
I wonder if debug kernel will give messages when a thread exits while
holding a mutex. Try it.
"Dh" <tt.dheeraj@gmail.com> wrote in message
news:1156957168.499731.212360@e3g2000cwe.googlegroups.com...
Alexander Grigoriev wrote:
Check if your structured exception handlers ever call exit() or
ExitThread(). See if you ever call TerminateThread. See if your
architecture
allows threads to die silently.
The thread in question is still running when the dead lock occured.
Check that you don't close the mutex handle while one thread is holding
it.
I suspect it also causes WAIT_ABANDONED. A mutex object is not actually
destroyed in the kernel while any thread is holding it, even if all
handles
are closed.
I am fairly certain that the close handle(we use CMutex objects) is
never called while somebody is using it. Still, I guess I will double
check that.
Don't use named mutexes, their names can collide with other programs,
unless
you really really want to share the mutex across processes.
Yes that is the intention - to share the mutexes across processes.
Abandoned mutex means you really cannot trust your protected data
internal
state. You might as well not use a mutex at all. Your best bet in that
case
is just abandon the data and restart the service.
Yes, so any thoughts on how to tackle this kind of problem? I am stuck
at this point, have run out of ideas to isolate the cause of this
problem.
Warm Regards,
Dheeraj