Re: WaitForSingleObject and Sleep never time out
- From: "Voidcoder" <voidcoder@xxxxxxxxx>
- Date: Mon, 6 Mar 2006 08:53:35 +0100
Well, does it show the same behaviour if you don't
initialize the interrupt? Just comment out InteruptInitialize
call and see if WaitForSingleObject returns with
timeout.
"ScottNichols" <ScottNichols@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6C257653-E38A-40FA-842E-B013DE0F3325@xxxxxxxxxxxxxxxx
After the Sleep you can debug other threads. The thread just stays in the
Slpg, RunBlkd state. It is as if the schedular has no timer running and
never wakes the thread back up.
The exact same problem is with the WaitForSingleObject timeout. The thread
will unblock if an event is signalled but not when it times out.
The problem is in the XSCCardDetectIstThread in the sdcontrol.c. I saw the
Sleep problem XSCInitialize function between the startTick and endtick
capture.
Cheers
"Voidcoder" wrote:
This is really interesting issue! Can you tell us some more details:
What happens with the rest of the system when your Sleep() hangs?
Are you still able to debug other threads?
Where are you calling it from (exact function name in sdcontrol.c)?
"ScottNichols" <ScottNichols@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:12531093-6E73-4B2E-A2BC-950151F2B970@xxxxxxxxxxxxxxxx
Yes - I create the event as follows:
pHardwareContext->hCardInsertInterruptEvent = CreateEvent(NULL, FALSE,
FALSE,NULL);
"Remi de Gravelaine" wrote:
Are you sure you are using an auto-reset event?
Remi
.
- References:
- Re: WaitForSingleObject and Sleep never time out
- From: Remi de Gravelaine
- Re: WaitForSingleObject and Sleep never time out
- From: Voidcoder
- Re: WaitForSingleObject and Sleep never time out
- Prev by Date: Re: increasing COM port using USB port
- Next by Date: Installation Error in PB 5.0
- Previous by thread: Re: WaitForSingleObject and Sleep never time out
- Next by thread: Display driver books
- Index(es):
Relevant Pages
|