Re: I HATE THREADS
Thanks, that helped. At least the app closes when the debugger is stopped.
But the app still hands in the send threads
WaitForSingleObject() call. Again the TRACE indicates that the thread has
exited.
The thread is created with AfxBeginThread() with m_AutoDelete set to FALSE.
Any ideas on why the thread exit process is apparently hung?
"Scott McPhillips [MVP]" <org-dot-mvps-at-scottmcp> wrote in message
news:OL2v0CUeGHA.3484@TK2MSFTNGP04.phx.gbl...
mike wrote:
Each thread has an exit event that tells the thread to stop and exit.
When I close the port I set the event and use this code to check for
thread termination.
if ( m_pSendThread )
{
m_pSendThread->m_bDone = TRUE;
m_pSendThread->Exit();
do
{
VERIFY(::GetExitCodeThread(m_pSendThread->m_hThread, &dwStatus));
}while( dwStatus == STILL_ACTIVE );
}
When this occurs, TRACE() information in the threads indicate that the
thread has exited but dwStatus remains STILL_ACTIVE. So I'm stuck in this
loop.
Get rid of the loop. Things like this suck up 100% of available CPU
cycles. This tends to lock up the debugger. Just do this...
WaitForSingleObject(m_pSendThread->m_hThread, INFINITE);
This does not consume CPU cyles while it is waiting.
--
Scott McPhillips [VC++ MVP]