- 14 Jan, 2009 32 commits
-
-
Michael Stefaniuc authored
-
Michael Stefaniuc authored
-
Henri Verbeet authored
-
Henri Verbeet authored
-
Henri Verbeet authored
-
Henri Verbeet authored
This is an internal wined3d function.
-
Henri Verbeet authored
It's never used.
-
Alexandre Julliard authored
-
Alexandre Julliard authored
-
Alistair Leslie-Hughes authored
-
Alistair Leslie-Hughes authored
-
Andrew Talbot authored
-
Hervé Chanal authored
-
Dmitry Timoshkov authored
-
Dmitry Timoshkov authored
-
Dmitry Timoshkov authored
-
Dmitry Timoshkov authored
-
Dmitry Timoshkov authored
-
Dmitry Timoshkov authored
-
Dmitry Timoshkov authored
-
Dmitry Timoshkov authored
-
Dmitry Timoshkov authored
-
Michael Stefaniuc authored
-
Michael Stefaniuc authored
-
Michael Stefaniuc authored
-
Michael Stefaniuc authored
-
Michael Stefaniuc authored
-
Michael Stefaniuc authored
-
Michael Stefaniuc authored
-
Michael Stefaniuc authored
-
Nikolay Sivov authored
-
André Hentschel authored
-
- 13 Jan, 2009 8 commits
-
-
Hans Leidekker authored
-
Alexandre Julliard authored
-
Alexandre Julliard authored
-
Stefan Dösinger authored
-
Stefan Dösinger authored
-
Nikolay Sivov authored
-
Ge van Geldorp authored
-
Ge van Geldorp authored
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.
-