PPC 2003 Thread
- From: Channa <Channa@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 13 Apr 2005 09:04:02 -0700
Hi,
I have an app created originally for PPC 2002 using eVC++ v3.0 and, it
has been migrated to PPC 2003 platform using eVC++ v4.0.
I have been noticing some odd behaviour since recently, and thought of
asking if anybody else have experienced the same and worked around already? I
have a separate thread reading the COM port. I am noticing that although this
thread exit normally, the main process do not get signaled state (using
WaitForSingleObject INFINITEly)!
I did trace using Kernel Tracker tool and noticed that the two threads
(main- and the COM-port-reading-thread) got blocked. I used to use "return"
for exiting the COM port reading thread. So, I changed it to ExitThread(),
and now, the COM port reading thread get terminated but the main process do
not get signaled and the Kernel Tracker tool shows that my main thread is
still being blocked. I have no idea is to why?
Any input would be appreciated.
Thanks in advance,
-Channa.
.
- Follow-Ups:
- Re: PPC 2003 Thread
- From: Paul G. Tobey [eMVP]
- Re: PPC 2003 Thread
- Prev by Date: Equivalent of byte in eVC++
- Next by Date: Re: PPC 2003 Thread
- Previous by thread: Equivalent of byte in eVC++
- Next by thread: Re: PPC 2003 Thread
- Index(es):
Relevant Pages
|
Loading
