> From: Paul Vriens [mailto:paul.vriens.w...@gmail.com]
>
> 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.
I'm n
> From: Rob Shearman [mailto:robertshear...@gmail.com]
>
> 2009/1/12 Alexandre Julliard :
> > "Ge van Geldorp" writes:
> > >
> > > Changelog:
> > > NdrVaryingArrayUnmarshall() is broken on Windows
> >
> > If it's broken on Windows then there's no point in testing
> > it, you can simply remove
"Rob Shearman" writes:
> 2009/1/12 Alexandre Julliard :
>> "Ge van Geldorp" 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 Microsof
Rob Shearman wrote:
> 2009/1/12 Alexandre Julliard :
>> "Ge van Geldorp" 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 too
2009/1/12 Alexandre Julliard :
> "Ge van Geldorp" 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 s
"Ge van Geldorp" 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 viola
