wild pointers in current named pipe implementation?
dank at kegel.com
Tue Apr 15 00:34:57 CDT 2003
In fact, here's the smallest program that reproduces the
problem for me:
1, 1024, 1024, NMPWAIT_USE_DEFAULT_WAIT, NULL));
I believe this will run fine on real Windows, and that
both calls will succeed there. I verified that FlushFileBuffers
returns nonzero on Win2K even when calling it on a just-created
pipe nobody had ever connected to. Thus I think Bill's patch
is probably a bit wrong; if fd is NULL, it should just say
"OK, I flushed" rather than returning a windows error.
More information about the wine-devel