Re: Reading Serial Port
"clinisbut" <clinisbut@gmail.com> wrote in message
news:e3bd3c90-b885-4c06-b526-65070a47e425@s12g2000prg.googlegroups.com...
Ok, I tried this:
I created two new events: ReaderStoped and WriterStoped.
In my reader-worker-thread:
Once the shutdown event is signaled, the loop breaks and reaches
this line:
SetEvent( ReaderStoped );
Same with Writer method.
Then, in my stop() method:
SetEvent(ShutdownEvent);
WaitForSingleObject( ReaderStoped, INFINITE ); //Just for
testing, I know I should call WaitForMultipleObjects with the events
ReaderStoped and WriterStoped.
CloseHandle( ShutdownEvent );
CloseHandle( hComm );
CloseHandle( ReadEvent );
CloseHandle( WriteEvent );
CloseHandle( ReaderStoped );
CloseHandle( WriterStoped );
PostQuitMessage( 0 );
Why did you introduce the new 'Stoped' events? You had it right in the
previous message: WaitForSingleObject should wait on the thread handle.
These new events just add complexity and needlessly duplicate built-in
functionality.
And, as explained in my previous reply, you are not calling PostQuitMessage
from the thread that is quitting.
Here is a recipe, assuming that the CWinThread m_bAutoDelete is set to FALSE
at startup.
How to shut down a worker thread:
main thread does SetEvent(ShutdownEvent)
main thread does WFSO(pthread->m_hThread)
worker thread senses ShutdownEvent with WFSO.
worker thread returns from thread function.
main thread WFSO returns
main thread closes handles
main thread delete pthread
How to shut down a message-driven thread:
main thread PostThreadMessage with shut down message
main thread does WFSO(pthread->m_hThread)
thread sees message, calls PostQuitMessage
main thread WFSO returns
main thread closes handles
main thread delete pthread
--
Scott McPhillips [VC++ MVP]