I've located a problem where when the exec issues a select() blocking for input for a socket and the select eats 100% of the CPU. Has any of the other windows programmers seen anything like this before? Without rewriting the code down to native, any ideas how to fix this?

David
--
.............................................................................
David L. Thompson                          The University of Montana
mailto:[EMAIL PROTECTED]                 Computer Science Department
http://www.cs.umt.edu/u/dthompsn           Missoula, MT  59812
                                           Work Phone : (406)257-8530

Reply via email to