[Bug 36636] New: valgrind shows an uninitialized write in shell32/tests/appbar.c
wine-bugs at winehq.org
wine-bugs at winehq.org
Sun Jun 1 18:02:16 CDT 2014
https://bugs.winehq.org/show_bug.cgi?id=36636
Bug ID: 36636
Summary: valgrind shows an uninitialized write in
shell32/tests/appbar.c
Product: Wine
Version: 1.7.19
Hardware: x86
OS: Linux
Status: NEW
Keywords: download, source, testcase
Severity: normal
Priority: P2
Component: shell32
Assignee: wine-bugs at winehq.org
Reporter: austinenglish at gmail.com
==20270== Syscall param writev(vector[...]) points to uninitialised byte(s)
==20270== at 0x4E952886: writev (in /usr/lib/libc-2.18.so)
==20270== by 0x7BC7FE6F: send_request (server.c:213)
==20270== by 0x7BC80001: wine_server_call (server.c:294)
==20270== by 0x5254AF8: put_message_in_queue (message.c:3141)
==20270== by 0x5254EA9: send_inter_thread_message (message.c:3209)
==20270== by 0x525518A: send_message (message.c:3277)
==20270== by 0x52555D1: SendMessageTimeoutW (message.c:3414)
==20270== by 0x4D221BC: SHAppBarMessage (appbar.c:142)
==20270== by 0x4A59513: test_setpos (appbar.c:222)
==20270== by 0x4A5ABF9: func_appbar (appbar.c:442)
==20270== by 0x4AB44E4: run_test (test.h:584)
==20270== by 0x4AB48D3: main (test.h:654)
==20270== Address 0x4cdfb20 is on thread 1's stack
==20270== Uninitialised value was created by a stack allocation
==20270== at 0x4A5940F: test_setpos (appbar.c:203)
==20270==
--
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.
More information about the wine-bugs
mailing list