[Bug 36344] valgrind shows some uninitialized memory use in ddraw/tests/ddraw7.c

[wine-bugs at winehq.org]

https://bugs.winehq.org/show_bug.cgi?id=36344

--- Comment #1 from Austin English <austinenglish at gmail.com> ---
A second one:
==32661== Conditional jump or move depends on uninitialised value(s)
==32661==    at 0x5832378: GetRegionData (region.c:889)
==32661==    by 0x4A9B6BE: ddraw_clipper_GetClipList (clipper.c:213)
==32661==    by 0x4AC95EE: ddraw_surface7_Blt (surface.c:1429)
==32661==    by 0x4DC374E: test_surface_discard (ddraw7.c:4938)
==32661==    by 0x4DDF4D1: func_ddraw7 (ddraw7.c:7063)
==32661==    by 0x4E096DC: run_test (test.h:584)
==32661==    by 0x4E09ACB: main (test.h:654)
==32661==  Uninitialised value was created by a stack allocation
==32661==    at 0x4AC9411: ddraw_surface7_Blt (surface.c:1503)
==32661==

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.