ole32: Don't get the HRESULT from the buffer if we get an RPC_S_CALL_FAILED…

ole32: Don't get the HRESULT from the buffer if we get an RPC_S_CALL_FAILED status back from the runtime. The buffer might not contain any data and nowhere in our ole32 code passes HRESULTs in the buffer.

ole32: Don't get the HRESULT from the buffer if we get an RPC_S_CALL_FAILED…
ee2250bc · Rob Shearman · Alexandre Julliard · 53f5d673 · ee2250bc
Commit ee2250bc authored Jan 21, 2008 by Rob Shearman Committed by Alexandre Julliard Jan 22, 2008
Hide whitespace changes
Inline Side-by-side

Showing with 1 addition and 5 deletions

rpc.c dlls/ole32/rpc.c +1 -5

No files found.
--- a/dlls/ole32/rpc.c
+++ b/dlls/ole32/rpc.c
@@ -893,12 +893,8 @@ static HRESULT WINAPI ClientRpcChannelBuffer_SendReceive(LPRPCCHANNELBUFFER ifac
    orpcthat.flags = ORPCF_NULL;
    orpcthat.extensions = NULL;

-    /* for normal RPC calls, faults are returned in first 4 bytes of the
-     * buffer */
    TRACE("RPC call status: 0x%lx\n", status);
-    if (status == RPC_S_CALL_FAILED)
-        hrFault = *(HRESULT *)olemsg->Buffer;
-    else if (status != RPC_S_OK)
+    if (status != RPC_S_OK)
        hr = HRESULT_FROM_WIN32(status);

    TRACE("hrFault = 0x%08x\n", hrFault);