[PATCH 3/3] rpcrt4: Reduce the timeout of waiting on the stop event in the server test to one second.

Rob Shearman robertshearman at gmail.com
Sat Jun 14 10:42:32 CDT 2008


The stop event should already be signaled by the time we get to that
point since we wait until the child processes terminate in the server
process and the stop event is signaled in the context of one of the
child processes.

Don't call RpcMgmtWaitServerListening if the call to
WaitForSingleObject failed since it is likely that s_stop() hasn't
been called and therefore the call to RpcMgmtWaitServerListening won't
ever return.
---
 dlls/rpcrt4/tests/server.c |   15 +++++++++++----
 1 files changed, 11 insertions(+), 4 deletions(-)

Interestingly, the server tests crash on Windows for me when I compile
them myself. Even more interesting is that the test appears to
highlight a Windows bug in NdrVaryingArrayUnmarshall when using
embedded pointers. This is because Windows' implementation of
NdrVaryingArrayUnmarshall doesn't set StubMsg->MaxCount using the
unmarshalled conformance, but it is used when unmarshalling embedded
pointers.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 7720d763349102490e0b3aab42614b88a74217d7.diff
Type: text/x-patch
Size: 1338 bytes
Desc: not available
Url : http://www.winehq.org/pipermail/wine-patches/attachments/20080614/8ba042bf/attachment-0001.bin 


More information about the wine-patches mailing list