New subject: [Bug 36705] valgrind shows uninitialized memory use in user32/tests/input.c

9 Jun 2014


      https://bugs.winehq.org/show_bug.cgi?id=36705
Bug ID: 36705
           Summary: valgrind shows uninitialized memory use in
                    user32/tests/input.c
           Product: Wine
           Version: 1.7.19
          Hardware: x86
                OS: Linux
            Status: NEW
          Keywords: download, source, testcase, valgrind
          Severity: normal
          Priority: P2
         Component: user32
          Assignee: wine-bugs@winehq.org
          Reporter: austinenglish@gmail.com
I tracked this down to only occurring when the screen is locked. Note that the
test passes with the screen locked or unlocked.
==15374== Conditional jump or move depends on uninitialised value(s)
==15374==    at 0x4F58C24: wine_dbgstr_wn (test.h:486)
==15374==    by 0x4EB30DC: wine_dbgstr_w (test.h:69)
==15374==    by 0x4EB87DB: test_key_names (input.c:1642)
==15374==    by 0x4EB88E7: func_input (input.c:1664)
==15374==    by 0x4F59107: run_test (test.h:584)
==15374==    by 0x4F594F2: main (test.h:654)
==15374==  Uninitialised value was created by a stack allocation
==15374==    at 0x4EB8871: func_input (input.c:1647)
==15374==
==15374== Conditional jump or move depends on uninitialised value(s)
==15374==    at 0x4F58C24: wine_dbgstr_wn (test.h:486)
==15374==    by 0x4EB30DC: wine_dbgstr_w (test.h:69)
==15374==    by 0x4EB8828: test_key_names (input.c:1643)
==15374==    by 0x4EB88E7: func_input (input.c:1664)
==15374==    by 0x4F59107: run_test (test.h:584)
==15374==    by 0x4F594F2: main (test.h:654)
==15374==  Uninitialised value was created by a stack allocation
==15374==    at 0x4EB8871: func_input (input.c:1647)
==15374==
-- 
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 36705] New: valgrind shows uninitialized memory use in user32/tests/input.c