On Tue, 14 Mar 2000, Matthew Cline wrote:
> I've looked into it some more, and it doesn't look like the
> problem is that the socket is being polled repeatedly after
> POLLHUP has been set; it's not locking up the wineserver or
> anything.
I know, the wineserver is still operational while in a busy loop (it makes
good use of the 100% CPU it's using), but it's different with the app - if
a WSAAsyncSelect was active on the socket, the application would get
flooded with FD_CLOSE notification and thus could not get anything done.
But you say that's not the case, the socket isn't even *connected* when
things go haywire? Yes, that would certainly be strange...
But I'm not quite sure that you handle strace correctly. At least use
strace -f. When you do strace wine (without -f), you are pretty much only
tracing the wineserver, not the client processes that do the real work
(like calling connect() etc).
