[Bug 38445] New: valgrind shows a couple invalid writes in kernel32/tests/fiber.c
https://bugs.winehq.org/show_bug.cgi?id=38445 Bug ID: 38445 Summary: valgrind shows a couple invalid writes in kernel32/tests/fiber.c Product: Wine Version: 1.7.41 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase, valgrind Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: --- ==9350== Use of uninitialised value of size 4 ==9350== at 0x7B83ACDD: SwitchToFiber (fiber.c:213) ==9350== by 0x48AC93A: test_FiberHandling (fiber.c:131) ==9350== by 0x48AD1A8: func_fiber (fiber.c:225) ==9350== by 0x49644EC: run_test (test.h:584) ==9350== by 0x4964926: main (test.h:666) ==9350== Uninitialised value was created by a stack allocation ==9350== at 0x425819D: __longjmp (__longjmp.S:55) ==9350== ==9350== Use of uninitialised value of size 4 ==9350== at 0x7B83ACDD: SwitchToFiber (fiber.c:213) ==9350== by 0x49727E3: ??? (in /home/austin/wine-valgrind/dlls/kernel32/tests/kernel32_test.exe.so) ==9350== by 0x48AD1A8: func_fiber (fiber.c:225) ==9350== by 0x49644EC: run_test (test.h:584) ==9350== by 0x4964926: main (test.h:666) ==9350== Uninitialised value was created by a stack allocation ==9350== at 0x425819D: __longjmp (__longjmp.S:55) ==9350== ==9350== Use of uninitialised value of size 4 ==9350== at 0x402A7E7: rindex (vg_replace_strmem.c:190) ==9350== by 0x496392C: winetest_set_location (test.h:282) ==9350== by 0x48AC951: test_FiberHandling (fiber.c:132) ==9350== by 0x48AD1A8: func_fiber (fiber.c:225) ==9350== by 0x49644EC: run_test (test.h:584) ==9350== by 0x4964926: main (test.h:666) ==9350== Uninitialised value was created by a stack allocation ==9350== at 0x425819D: __longjmp (__longjmp.S:55) ==9350== -- 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.
https://bugs.winehq.org/show_bug.cgi?id=38445 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Debian -- 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.
https://bugs.winehq.org/show_bug.cgi?id=38445 --- Comment #1 from Austin English <austinenglish(a)gmail.com> --- ==8441== Use of uninitialised value of size 4 ==8441== at 0x48ACA26: GetLastError (winbase.h:2819) ==8441== by 0x48ACA26: test_FiberHandling (???:0) ==8441== by 0x48AD1A8: func_fiber (fiber.c:225) ==8441== by 0x49644EC: run_test (test.h:584) ==8441== by 0x4964926: main (test.h:666) ==8441== Uninitialised value was created by a stack allocation ==8441== at 0x425819D: __longjmp (__longjmp.S:55) ==8441== ==8441== Conditional jump or move depends on uninitialised value(s) ==8441== at 0x48ACCE5: test_FiberLocalStorage (fiber.c:182) ==8441== by 0x48AD1C4: func_fiber (fiber.c:227) ==8441== by 0x49644EC: run_test (test.h:584) ==8441== by 0x4964926: main (test.h:666) ==8441== Uninitialised value was created by a stack allocation ==8441== at 0x425819D: __longjmp (__longjmp.S:55) ==8441== ==8441== Use of uninitialised value of size 4 ==8441== at 0x48AD1C8: func_fiber (fiber.c:228) ==8441== by 0x49644EC: run_test (test.h:584) ==8441== by 0x4964926: main (test.h:666) ==8441== Uninitialised value was created by a stack allocation ==8441== at 0x425819D: __longjmp (__longjmp.S:55) ==8441== ==8441== Use of uninitialised value of size 4 ==8441== at 0x49649B7: __wine_spec_exe_entry (exe_entry.c:38) ==8441== Uninitialised value was created by a stack allocation ==8441== at 0x425819D: __longjmp (__longjmp.S:55) ==8441== -- 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.
https://bugs.winehq.org/show_bug.cgi?id=38445 Thomas Faller <tfaller1(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tfaller1(a)gmx.de --- Comment #2 from Thomas Faller <tfaller1(a)gmx.de> --- I can't reproduce this bug. Is this bug still present in your test runs? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=38445 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Austin English <austinenglish(a)gmail.com> --- (In reply to Thomas Faller from comment #2)
I can't reproduce this bug. Is this bug still present in your test runs?
Nope, thanks for checking. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=38445 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #4 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 1.7.55. -- 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.
participants (1)
-
wine-bugs＠winehq.org