Corinna Vinschen wrote:
On Jul 7 08:43, Darryl Miles wrote:
What was the reason the existing code in CVS for select.cc was disabled?
Maybe it would help to better understand the reasons/cases where the
disabled code failed.
Hangs with native Windows applications, AFAIR.
I take this to mean a CYGWIN app is on one end and a native app on the
other.
Remember the test case ?
When it hangs can you remember who was reading and who was writing.
Is there a native standard app in Win2k/XP that can be used ?
In MSDN there is:
"The pipe server should not perform a blocking read operation until the
pipe client has started. Otherwise, a race condition can occur. This
typically occurs when initialization code, such as the C run-time, needs
to lock and examine inherited handles."
Could this be related ? Does anyone on the list know the background of
the statement, it sounds like a Windows documented bug/feature.
How is the notion of Server or Client end given when both ends are only
using Open/Read/Write and never using CallNamedPipe, ConnectNamedPipe,
WaitNamedPipe. Is the creator automatically the server ?
Darryl
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
