rpcrt4/tests: Win 8 and 10 do not correctly unmarshal a ranged enum16.

In practice this bug is not observed since midl, unlike widl, does not generate ranges in inline stub mode. For interpreted stubs, where midl does generate ranges, the [out] parameters are zero-initialised by the runtime. Signed-off-by: Huw Davies <huw@codeweavers.com> Signed-off-by: Alexandre Julliard <julliard@winehq.org>

rpcrt4/tests: Win 8 and 10 do not correctly unmarshal a ranged enum16.
f53c320f · Huw Davies · Alexandre Julliard · b7e2e45f · f53c320f
Commit f53c320f authored Sep 06, 2016 by Huw Davies Committed by Alexandre Julliard Sep 07, 2016
Hide whitespace changes
Inline Side-by-side

Showing with 4 additions and 1 deletion

server.c dlls/rpcrt4/tests/server.c +4 -1

No files found.
--- a/dlls/rpcrt4/tests/server.c
+++ b/dlls/rpcrt4/tests/server.c
@@ -1006,8 +1006,11 @@ basic_tests(void)

  if (!old_windows_version)
  {
+      re = 0xdeadbeef;
      get_ranged_enum(&re);
-      ok(re == RE3, "get_ranged_enum() returned %d instead of RE3\n", re);
+      ok(re == RE3 ||
+         broken(re == MAKELONG(re, 0xdead)), /* Win 8, Win 10 */
+         "get_ranged_enum() returned %x instead of RE3\n", re);
  }
 }