-=> Quoting Bill Bond to all <=- 

 BB> I'm having trouble with one of my programs and I'm beginning to
 BB> wonder how reliable the DosWaitThread() function is.  What happens is
 BB> that every once and a while a thread will end but DosWaitThread()
 BB> doesn't return (both parameters are 0).  To test this I ran the
 BB> program from a cmd file in a loop so that it keeps running over and
 BB> over.  It'll run fine maybe 50 or 100 times (or more) but eventually a
 BB> call to DosWaitThread() doesn't return when it should, or so it seems.
 BB> I know the program is not locked up because I can terminate it with a
 BB> keypress.  One of the threads monitors the keyboard and returns when 
 BB> a predefined key is pressed.  In this case DosWaitThread() returns as
 BB> expected. 
 BB> Has anyone seen anything like this before?  I believe this started
 BB> happening around the time I upgraded to Warp, or possibly one of the
 BB> Warp fixpacks, but I'm not positive.  The program had been running ok
 BB> for some time before it started misbehaving. 
 BB> thanks,
 BB> Bill

I've noticed something like this.  My program has 6 threads running.
When I exit, I call DosWaitThread() to wait for each thread to
terminate.

Sometimes (1 in 50 or 100 as you mentioned) my program will hang and I
have to kill the program from the Tasklist after pressing Ctrl-Esc
twice.  It is always the same thread that hangs, and I'm not sure if its
hanging in DosWaitThread().

Are you using an exit list (DosExitList())?  I am not, but perhaps I
should be.

Phil - Fido:  1:124/8014.0 | Internet:  phil.crown{at}bluecafe.com


--- Blue Wave/OS2 v2.30