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

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

            Bug ID: 36587
           Summary: valgrind shows uninitialized memory use in
                    user32/tests/winstation.c
           Product: Wine
           Version: 1.7.19
          Hardware: x86
                OS: Linux
            Status: NEW
          Keywords: download, source, testcase
          Severity: normal
          Priority: P2
         Component: user32
          Assignee: wine-bugs(a)winehq.org
          Reporter: austinenglish(a)gmail.com

../../../tools/runtest -q -P wine -T ../../.. -M user32.dll -p
user32_test.exe.so winstation && touch winstation.ok
preloader: Warning: failed to reserve range 00110000-68000000
preloader: Warning: failed to reserve range 7f000000-82000000
==25156== Syscall param write(buf) points to uninitialised byte(s)
==25156==    at 0x4226CF3: __write_nocancel (syscall-template.S:81)
==25156==    by 0x7BC7FD72: send_request (server.c:198)
==25156==    by 0x7BC7FF91: wine_server_call (server.c:294)
==25156==    by 0x519D2EE: send_hardware_message (message.c:3331)
==25156==    by 0x5173BEB: SendInput (input.c:185)
==25156==    by 0x4D9FB49: test_inputdesktop (winstation.c:530)
==25156==    by 0x4DA2430: func_winstation (winstation.c:939)
==25156==    by 0x4DA3978: run_test (test.h:584)
==25156==    by 0x4DA3D67: main (test.h:654)
==25156==  Address 0x510f6a8 is on thread 1's stack
==25156==  Uninitialised value was created by a stack allocation
==25156==    at 0x4D9F748: test_inputdesktop (winstation.c:492)
==25156==

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

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

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

Austin English <austinenglish(a)gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |valgrind

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

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

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

--- Comment #1 from Austin English <austinenglish(a)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.