rpcrt4/tests: NdrVaryingArrayUnmarshall() is broken on Windows

[Paul Vriens]

Rob Shearman wrote:
> 2009/1/12 Alexandre Julliard <julliard at winehq.org>:
>> "Ge van Geldorp" <ge at gse.nl> writes:
>>
>>> The failures in rpcrt4:server on Windows are caused by an access violation
>>> thrown in NdrVaryingArrayUnmarshall() called from get_5numbers(). I've
>>> created a minimum get_5numbers() test with Microsoft tools and that throws
>>> the same access violation. The access violation disappears when zeroing
>>> out the StubMsg before calling NdrClientInitializeNew(), so my guess is
>>> Windows NdrVaryingArrayUnmarshall() uses an uninitialized member.
>>>
>>> Changelog:
>>>   NdrVaryingArrayUnmarshall() is broken on Windows
>> If it's broken on Windows then there's no point in testing it, you can
>> simply remove it.
> 
> There's value in the function working in Wine and testing the function
> stops it being inadvertently broken (probably by me). Microsoft may
> release a patch to fix it or fix it in a more recent version of
> Windows.
> 

It looks like we've had exceptions on anything but XP and W2K3 for a long time. 
The exceptions (as reported on test.winehq.org) for XP and W2K3 started 
happening after the move to use winetest.exe from test.winehq.org.

-- 
Cheers,

Paul.