[Bug 36282] New: valgrind shows an unitialized write in ieframe/tests/ie.c

[wine-bugs at winehq.org]

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

            Bug ID: 36282
           Summary: valgrind shows an unitialized write in
                    ieframe/tests/ie.c
           Product: Wine
           Version: 1.3.13
          Hardware: x86
                OS: Linux
            Status: NEW
          Keywords: download, source, testcase
          Severity: minor
          Priority: P2
         Component: ieframe
          Assignee: wine-bugs at winehq.org
          Reporter: austinenglish at gmail.com

==16468== Thread 6:
==16468== Syscall param write(buf) points to uninitialised byte(s)
==16468==    at 0x4EA8262B: ??? (in /usr/lib/libpthread-2.18.so)
==16468==    by 0x7BC46BB8: NtWriteFile (file.c:1073)
==16468==    by 0x7B83E0AA: WriteFile (file.c:563)
==16468==    by 0x5A01BB8: rpcrt4_conn_np_write (rpc_transport.c:444)
==16468==    by 0x59F6B27: rpcrt4_conn_write (rpc_binding.h:189)
==16468==    by 0x59F8AA9: RPCRT4_SendWithAuth (rpc_message.c:849)
==16468==    by 0x59F9BA0: RPCRT4_Send (rpc_message.c:1245)
==16468==    by 0x59FCD02: process_request_packet (rpc_server.c:464)
==16468==    by 0x59FCF82: RPCRT4_process_packet (rpc_server.c:519)
==16468==    by 0x59FD115: RPCRT4_worker_thread (rpc_server.c:541)
==16468==    by 0x7BC909EA: worker_thread_proc (threadpool.c:110)
==16468==    by 0x7BC87087: ??? (signal_i386.c:2571)
==16468==    by 0x7BC870D0: call_thread_func (signal_i386.c:2630)
==16468==    by 0x7BC87065: ??? (signal_i386.c:2571)
==16468==    by 0x7BC8E4B0: start_thread (thread.c:428)
==16468==    by 0x4EA7BD89: start_thread (in /usr/lib/libpthread-2.18.so)
==16468==    by 0x4E95CA0D: clone (in /usr/lib/libc-2.18.so)
==16468==  Address 0x47f9cf4 is 44 bytes inside a recently re-allocated block
of size 92 alloc'd
==16468==    at 0x7BC4C735: notify_alloc (heap.c:255)
==16468==    by 0x7BC50F79: RtlAllocateHeap (heap.c:1716)
==16468==    by 0x59F88E9: RPCRT4_SendWithAuth (rpc_message.c:808)
==16468==    by 0x59F9BA0: RPCRT4_Send (rpc_message.c:1245)
==16468==    by 0x59FCD02: process_request_packet (rpc_server.c:464)
==16468==    by 0x59FCF82: RPCRT4_process_packet (rpc_server.c:519)
==16468==    by 0x59FD115: RPCRT4_worker_thread (rpc_server.c:541)
==16468==    by 0x7BC909EA: worker_thread_proc (threadpool.c:110)
==16468==    by 0x7BC87087: ??? (signal_i386.c:2571)
==16468==    by 0x7BC870D0: call_thread_func (signal_i386.c:2630)
==16468==    by 0x7BC87065: ??? (signal_i386.c:2571)
==16468==    by 0x7BC8E4B0: start_thread (thread.c:428)
==16468==    by 0x4EA7BD89: start_thread (in /usr/lib/libpthread-2.18.so)
==16468==    by 0x4E95CA0D: clone (in /usr/lib/libc-2.18.so)
==16468==  Uninitialised value was created by a client request
==16468==    at 0x7BC4C52C: mark_block_uninitialized (heap.c:209)
==16468==    by 0x7BC4C697: initialize_block (heap.c:240)
==16468==    by 0x7BC50FA3: RtlAllocateHeap (heap.c:1717)
==16468==    by 0x501E635: IMalloc_fnAlloc (ifs.c:186)
==16468==    by 0x501EF50: CoTaskMemAlloc (objidl.h:1236)
==16468==    by 0x505C935: RemUnknown_RemQueryInterface (stubmanager.c:690)
==16468==    by 0x50661C6: IRemUnknown_RemQueryInterface_Stub (dcom_p.c:369)
==16468==    by 0x59CA5BF: CStdStubBuffer_Invoke (cstub.c:477)
==16468==    by 0x503D280: RPC_ExecuteCall (objidl.h:9086)
==16468==    by 0x4FFC1ED: apartment_wndproc (compobj.c:1460)
==16468==    by 0x548C509: ??? (winproc.c:173)
==16468==    by 0x548C67E: call_window_proc (winproc.c:244)
==16468==    by 0x548E817: WINPROC_call_window (winproc.c:900)
==16468==    by 0x544FBE4: DispatchMessageW (message.c:4019)
==16468==    by 0x4793F60: IEWinMain (iexplore.c:1061)
==16468==    by 0x472CA34: wWinMain (main.c:84)
==16468==    by 0x472CD21: wmain (exe_wmain.c:51)
==16468==    by 0x472CBFC: __wine_spec_exe_wentry (exe_wentry.c:36)
==16468==    by 0x7B864247: ??? (process.c:1045)
==16468==    by 0x7B864394: start_process (process.c:1097)
==16468==

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