[Bug 36603] valgrind shows uninitialized memory use in winspool.drv/tests/info.c

[wine-bugs at winehq.org]

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

--- Comment #1 from Austin English <austinenglish at gmail.com> ---
Also:
==15338== Syscall param write(buf) points to uninitialised byte(s)
==15338==    at 0x4226CF3: __write_nocancel (syscall-template.S:81)
==15338==    by 0x7BC7FD72: send_request (server.c:198)
==15338==    by 0x7BC7FF91: wine_server_call (server.c:294)
==15338==    by 0x7BC6348E: close_handle (om.c:355)
==15338==    by 0x7BC634C2: NtClose (om.c:376)
==15338==    by 0x5697421: RegCloseKey (registry.c:1083)
==15338==    by 0x4F8E22C: OpenPrinterW (info.c:2558)
==15338==    by 0x4F8E01C: OpenPrinterA (info.c:2495)
==15338==    by 0x4E518C8: test_EnumForms (info.c:808)
==15338==    by 0x4E5C438: func_info (info.c:3031)
==15338==    by 0x4E5D2B1: run_test (test.h:584)
==15338==    by 0x4E5D69F: main (test.h:654)
==15338==  Address 0x4f6f9cc is on thread 1's stack
==15338==  Uninitialised value was created by a stack allocation
==15338==    at 0x4F8E091: OpenPrinterW (info.c:2532)
==15338==

-- 
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.