[Bug 36587] valgrind shows uninitialized memory use in user32/tests/ winstation.c

[wine-bugs at winehq.org]

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

--- Comment #1 from Austin English <austinenglish at gmail.com> ---
Still in 4.0-rc3:
==22229== Syscall param write(buf) points to uninitialised byte(s)
==22229==    at 0x424EC7F: write (write.c:27)
==22229==    by 0x7BC75413: send_request (server.c:213)
==22229==    by 0x7BC76158: server_call_unlocked (server.c:288)
==22229==    by 0x7BC761AD: wine_server_call (server.c:321)
==22229==    by 0x4E93552: send_hardware_message (message.c:3362)
==22229==    by 0x4E7614A: SendInput (input.c:197)
==22229==    by 0x4B60D2D: test_inputdesktop (winstation.c:600)
==22229==    by 0x4B65B26: func_winstation (winstation.c:1015)
==22229==    by 0x4B6646D: run_test (test.h:617)
==22229==    by 0x4B66EAB: main (test.h:701)
==22229==  Address 0x4e1f808 is on thread 1's stack
==22229==  in frame #4, created by send_hardware_message (message.c:3319)
==22229==  Uninitialised value was created by a stack allocation
==22229==    at 0x4B609C8: test_inputdesktop (winstation.c:562)
==22229==

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