June 2014 - Wine-Bugs - list.winehq.org

[Bug 36306] New: valgrind shows a possible leak in netapi32/tests/wksta.c
by wine-bugs＠winehq.org June 3, 2014

June 3, 2014

https://bugs.winehq.org/show_bug.cgi?id=36306 Bug ID: 36306 Summary: valgrind shows a possible leak in netapi32/tests/wksta.c Product: Wine Version: 1.7.18 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: netapi32 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==30938== 64 bytes in 2 blocks are possibly lost in loss record 40 of 73 ==30938== at 0x7BC4C735: notify_alloc (heap.c:255) ==30938== by 0x7BC50F79: RtlAllocateHeap (heap.c:1716) ==30938== by 0x4C25EDC: ??? ==30938== by 0x4C33153: ??? ==30938== by 0x4C29723: ??? ==30938== by 0x4C29B00: ??? ==30938== by 0x4C3351B: ??? ==30938== by 0x4C33751: ??? ==30938== by 0x4C29ABA: ??? ==30938== by 0x4C3351B: ??? ==30938== by 0x4C3362E: ??? ==30938== by 0x4C2E6E4: ??? ==30938== by 0x4957493: run_wkstatransportenum_tests (wksta.c:152) ==30938== by 0x4957AB6: func_wksta (wksta.c:237) ==30938== by 0x49588C0: run_test (test.h:584) ==30938== by 0x4958CAF: main (test.h:654) ==30938== 64 bytes in 2 blocks are possibly lost in loss record 41 of 73 ==30938== at 0x7BC4C735: notify_alloc (heap.c:255) ==30938== by 0x7BC50F79: RtlAllocateHeap (heap.c:1716) ==30938== by 0x7BC39AE9: RtlInitializeCriticalSectionEx (critsection.c:326) ==30938== by 0x7B876B51: InitializeCriticalSectionEx (sync.c:356) ==30938== by 0x7B876AD0: InitializeCriticalSection (sync.c:313) ==30938== by 0x4C33177: ??? ==30938== by 0x4C29723: ??? ==30938== by 0x4C29B00: ??? ==30938== by 0x4C3351B: ??? ==30938== by 0x4C33751: ??? ==30938== by 0x4C29ABA: ??? ==30938== by 0x4C3351B: ??? ==30938== by 0x4C3362E: ??? ==30938== by 0x4C2E6E4: ??? ==30938== by 0x4957493: run_wkstatransportenum_tests (wksta.c:152) ==30938== by 0x4957AB6: func_wksta (wksta.c:237) ==30938== by 0x49588C0: run_test (test.h:584) ==30938== by 0x4958CAF: main (test.h:654) ==30938== -- 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.

1 1

[Bug 36325] New: valgrind shows a couple possible leaks in rpcrt4/tests/server.c
by wine-bugs＠winehq.org June 3, 2014

June 3, 2014

https://bugs.winehq.org/show_bug.cgi?id=36325 Bug ID: 36325 Summary: valgrind shows a couple possible leaks in rpcrt4/tests/server.c Product: Wine Version: 1.7.18 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==459== 64 bytes in 1 blocks are possibly lost in loss record 172 of 352 ==459== at 0x7BC4C735: notify_alloc (heap.c:255) ==459== by 0x7BC50F79: RtlAllocateHeap (heap.c:1716) ==459== by 0x55F927B: rpcrt4_protseq_np_alloc (rpc_transport.c:642) ==459== by 0x55F5366: alloc_serverprotoseq (rpc_server.c:927) ==459== by 0x55F5610: RPCRT4_get_or_create_serverprotseq (rpc_server.c:977) ==459== by 0x55F5709: RpcServerUseProtseqEpExA (rpc_server.c:997) ==459== by 0x55F51E2: RpcServerUseProtseqEpA (rpc_server.c:892) ==459== by 0x4973259: server (server.c:1622) ==459== by 0x49737B1: func_server (server.c:1718) ==459== by 0x4995124: run_test (test.h:584) ==459== by 0x4995513: main (test.h:654) ==459== -- 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.

1 1

[Bug 36585] New: valgrind shows uninitialized memory use in user32/tests/edit.c
by wine-bugs＠winehq.org June 3, 2014

June 3, 2014

https://bugs.winehq.org/show_bug.cgi?id=36585 Bug ID: 36585 Summary: valgrind shows uninitialized memory use in user32/tests/edit.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 edit && touch edit.ok preloader: Warning: failed to reserve range 00110000-68000000 preloader: Warning: failed to reserve range 7f000000-82000000 ==4864== Use of uninitialised value of size 4 ==4864== at 0x403DC86: mbstowcs_sbcs (mbtowc.c:88) ==4864== by 0x403E430: wine_cp_mbstowcs (mbtowc.c:278) ==4864== by 0x7B850B05: MultiByteToWideChar (locale.c:2031) ==4864== by 0x52560FB: EDIT_EM_SetHandle (edit.c:2821) ==4864== by 0x525C68C: EditWndProc_common (edit.c:4728) ==4864== by 0x52CDFCA: EditWndProcA (winproc.c:1077) ==4864== by 0x52CB4F5: ??? (winproc.c:173) ==4864== by 0x52CB66A: call_window_proc (winproc.c:244) ==4864== by 0x52CD8B9: WINPROC_call_window (winproc.c:909) ==4864== by 0x528A11C: call_window_proc (message.c:2223) ==4864== by 0x528CFBA: send_message (message.c:3260) ==4864== by 0x528D649: SendMessageA (message.c:3476) ==4864== by 0x4DD5C07: test_EM_GETHANDLE (edit.c:2700) ==4864== by 0x4DD61E2: func_edit (edit.c:2785) ==4864== by 0x4E93978: run_test (test.h:584) ==4864== by 0x4E93D67: main (test.h:654) ==4864== Uninitialised value was created by a client request ==4864== at 0x7BC4C4D6: mark_block_uninitialized (heap.c:209) ==4864== by 0x7BC4C641: initialize_block (heap.c:240) ==4864== by 0x7BC50F4D: RtlAllocateHeap (heap.c:1717) ==4864== by 0x7B8457FF: HeapAlloc (heap.c:271) ==4864== by 0x7B845B34: GlobalAlloc (heap.c:388) ==4864== by 0x7B846E63: LocalAlloc (heap.c:967) ==4864== by 0x4DD5AD5: test_EM_GETHANDLE (edit.c:2686) ==4864== by 0x4DD61E2: func_edit (edit.c:2785) ==4864== by 0x4E93978: run_test (test.h:584) ==4864== by 0x4E93D67: main (test.h:654) ==4864== -- 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.

1 1

[Bug 36574] New: valgrind shows a definite leak in urlmon/tests/protocol.c
by wine-bugs＠winehq.org June 3, 2014

June 3, 2014

https://bugs.winehq.org/show_bug.cgi?id=36574 Bug ID: 36574 Summary: valgrind shows a definite leak in urlmon/tests/protocol.c Product: Wine Version: 1.7.19 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: urlmon Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==21884== 96 bytes in 1 blocks are definitely lost in loss record 552 of 841 ==21884== at 0x7BC4C6DF: notify_alloc (heap.c:255) ==21884== by 0x7BC50F23: RtlAllocateHeap (heap.c:1716) ==21884== by 0x6430124: heap_alloc_zero (internet.h:121) ==21884== by 0x6431091: create_netconn (netconnection.c:369) ==21884== by 0x641FDBC: open_http_connection (http.c:4789) ==21884== by 0x6420432: HTTP_HttpSendRequestW (http.c:4916) ==21884== by 0x64211FA: AsyncHttpSendRequestProc (http.c:5182) ==21884== by 0x642DD83: INTERNET_WorkerThreadFunc (internet.c:3840) ==21884== by 0x7BC90A24: worker_thread_proc (threadpool.c:110) ==21884== by 0x7BC870C7: ??? (signal_i386.c:2571) ==21884== by 0x7BC87110: call_thread_func (signal_i386.c:2630) ==21884== by 0x7BC870A5: ??? (signal_i386.c:2571) ==21884== by 0x7BC8E4EC: start_thread (thread.c:428) ==21884== by 0x421FF92: start_thread (pthread_create.c:309) ==21884== by 0x43247ED: clone (clone.S:129) ==21884== -- 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.

1 1

[Bug 36393] New: valgrind shows a possible leak in infosoft/tests/infosoft.c
by wine-bugs＠winehq.org June 3, 2014

June 3, 2014

https://bugs.winehq.org/show_bug.cgi?id=36393 Bug ID: 36393 Summary: valgrind shows a possible leak in infosoft/tests/infosoft.c Product: Wine Version: 1.7.18 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ../../../tools/runtest -q -P wine -T ../../.. -M infosoft.dll -p infosoft_test.exe.so infosoft && touch infosoft.ok preloader: Warning: failed to reserve range 00110000-68000000 preloader: Warning: failed to reserve range 7f000000-82000000 ==21605== 28 bytes in 1 blocks are possibly lost in loss record 157 of 548 ==21605== at 0x7BC508EB: RtlAllocateHeap (heap.c:255) ==21605== by 0x5062BE8: apartment_getclassobject (compobj.c:526) ==21605== by 0x5065FF6: get_inproc_class_object (compobj.c:2894) ==21605== by 0x5068D5F: CoGetClassObject (compobj.c:3032) ==21605== by 0x50694E7: CoCreateInstance (compobj.c:3197) ==21605== by 0x4AA23CE: func_infosoft (infosoft.c:167) ==21605== by 0x4AA285A: run_test (test.h:584) ==21605== by 0x4AA1C8E: main (test.h:654) ==21605== -- 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.

1 1

[Bug 36219] New: valgrind shows some definite leaks in dlls/jscript/tests/run.c
by wine-bugs＠winehq.org June 3, 2014

June 3, 2014

https://bugs.winehq.org/show_bug.cgi?id=36219 Bug ID: 36219 Summary: valgrind shows some definite leaks in dlls/jscript/tests/run.c Product: Wine Version: 1.7.17 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: jscript Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Created attachment 48354 --> https://bugs.winehq.org/attachment.cgi?id=48354 valgrind log Unfortunately, not getting very good stack traces, even with -O0 and an unstripped gecko build: ==27187== 32 bytes in 1 blocks are definitely lost in loss record 4,576 of 15,293 ==27187== at 0x7BC4C6B7: notify_alloc (heap.c:255) ==27187== by 0x7BC50EFB: RtlAllocateHeap (heap.c:1716) ==27187== by 0x69C350F: ??? ==27187== by 0x69C4488: ??? ==27187== by 0x69C7127: ??? ==27187== by 0x69C7912: ??? ==27187== by 0x69C5F2E: ??? ==27187== by 0x69C7D84: ??? ==27187== by 0x69C80C5: ??? ==27187== by 0x69C85F8: ??? ==27187== by 0x69E8695: ??? ==27187== by 0x4E5D234: parse_script (activscp.h:1290) ==27187== by 0x4E5F086: run_from_res (run.c:1814) ==27187== by 0x4E60FA5: run_tests (run.c:2162) ==27187== by 0x4E61EFD: func_run (run.c:2415) ==27187== by 0x4E62D5F: run_test (test.h:584) ==27187== by 0x4E6314E: main (test.h:654) ==27187== Also some possible leaks ==9457== 16 bytes in 1 blocks are possibly lost in loss record 1,052 of 15,293 ==9457== at 0x7BC4C6B7: notify_alloc (heap.c:255) ==9457== by 0x7BC50EFB: RtlAllocateHeap (heap.c:1716) ==9457== by 0x4FE80B4: alloc_bstr (oleaut.c:162) ==9457== by 0x4FE844A: SysAllocStringLen (oleaut.c:324) ==9457== by 0x4FE8161: SysAllocString (oleaut.c:232) ==9457== by 0x69C3E31: ??? ==9457== by 0x69C4139: ??? ==9457== by 0x69C6041: ??? ==9457== by 0x69C6088: ??? ==9457== by 0x69C7957: ??? ==9457== by 0x69C5F2E: ??? ==9457== by 0x69C7D84: ??? ==9457== by 0x69C80C5: ??? ==9457== by 0x69C85F8: ??? ==9457== by 0x69E8695: ??? ==9457== by 0x4E5D234: parse_script (activscp.h:1290) ==9457== by 0x4E5EAA4: parse_script_af (run.c:1692) ==9457== by 0x4E5EB0C: parse_script_a (run.c:1699) ==9457== by 0x4E607D3: run_tests (run.c:2070) ==9457== by 0x4E61EFD: func_run (run.c:2415) -- 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.

1 2

[Bug 36195] New: valgrind shows several leaks in dsound/tests/capture.c
by wine-bugs＠winehq.org June 3, 2014

June 3, 2014

https://bugs.winehq.org/show_bug.cgi?id=36195 Bug ID: 36195 Summary: valgrind shows several leaks in dsound/tests/capture.c Product: Wine Version: 1.7.17 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: directx-dsound Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==12144== 28 bytes in 1 blocks are possibly lost in loss record 196 of 816 ==12144== at 0x7BC4C6B7: notify_alloc (heap.c:255) ==12144== by 0x7BC50EFB: RtlAllocateHeap (heap.c:1716) ==12144== by 0x4FB883E: COMPOBJ_DllList_Add (compobj.c:526) ==12144== by 0x4FBAB7A: apartment_getclassobject (compobj.c:1335) ==12144== by 0x4FBE2C4: get_inproc_class_object (compobj.c:2894) ==12144== by 0x4FBE783: CoGetClassObject (compobj.c:3032) ==12144== by 0x4FBED45: CoCreateInstance (compobj.c:3197) ==12144== by 0x65A603C: get_mmdevenum (dsound_main.c:178) ==12144== by 0x65A636D: GetDeviceID (dsound_main.c:261) ==12144== by 0x659F7B5: DirectSoundCaptureDevice_Initialize (capture.c:1022) ==12144== by 0x65A07B9: IDirectSoundCaptureImpl_Initialize (capture.c:1284) ==12144== by 0x65A0B21: DirectSoundCaptureCreate (capture.c:1388) ==12144== by 0x4E4FA2E: test_COM (capture.c:692) ==12144== by 0x4E50145: func_capture (capture.c:775) ==12144== by 0x4E6C486: run_test (test.h:584) ==12144== by 0x4E6C875: main (test.h:654) ==12144== ==12144== 28 bytes in 1 blocks are possibly lost in loss record 204 of 816 ==12144== at 0x7BC4C6B7: notify_alloc (heap.c:255) ==12144== by 0x7BC50EFB: RtlAllocateHeap (heap.c:1716) ==12144== by 0x4FB883E: COMPOBJ_DllList_Add (compobj.c:526) ==12144== by 0x4FBAB7A: apartment_getclassobject (compobj.c:1335) ==12144== by 0x4FBE2C4: get_inproc_class_object (compobj.c:2894) ==12144== by 0x4FBE783: CoGetClassObject (compobj.c:3032) ==12144== by 0x4E4DAFA: test_capture (capture.c:189) ==12144== by 0x4E5014A: func_capture (capture.c:776) ==12144== by 0x4E6C486: run_test (test.h:584) ==12144== by 0x4E6C875: main (test.h:654) ==12144== ==12144== 846 bytes in 47 blocks are definitely lost in loss record 714 of 816 ==12144== at 0x7BC4C6B7: notify_alloc (heap.c:255) ==12144== by 0x7BC50EFB: RtlAllocateHeap (heap.c:1716) ==12144== by 0x65ADE25: DSOUND_CopyFormat (primary.c:447) ==12144== by 0x659E392: IDirectSoundCaptureBufferImpl_Create (capture.c:704) ==12144== by 0x65A0409: IDirectSoundCaptureImpl_CreateCaptureBuffer (capture.c:1232) ==12144== by 0x4E4F47E: dscenum_callback (capture.c:564) ==12144== by 0x65A665A: a_to_w_callback (dsound_main.c:319) ==12144== by 0x65A6F2B: enumerate_mmdevices (dsound_main.c:492) ==12144== by 0x65A73EF: DirectSoundCaptureEnumerateW (dsound_main.c:625) ==12144== by 0x65A72ED: DirectSoundCaptureEnumerateA (dsound_main.c:593) ==12144== by 0x4E4F90F: test_enumerate (capture.c:672) ==12144== by 0x4E5014F: func_capture (capture.c:777) ==12144== by 0x4E6C486: run_test (test.h:584) ==12144== by 0x4E6C875: main (test.h:654) ==12144== 88,200 bytes in 1 blocks are possibly lost in loss record 813 of 816 ==12144== at 0x7BC4C6B7: notify_alloc (heap.c:255) ==12144== by 0x7BC50EFB: RtlAllocateHeap (heap.c:1716) ==12144== by 0x659EC62: IDirectSoundCaptureBufferImpl_Create (capture.c:797) ==12144== by 0x65A0409: IDirectSoundCaptureImpl_CreateCaptureBuffer (capture.c:1232) ==12144== by 0x4E4FD44: test_COM (capture.c:727) ==12144== by 0x4E50145: func_capture (capture.c:775) ==12144== by 0x4E6C486: run_test (test.h:584) ==12144== by 0x4E6C875: main (test.h:654) ==12144== -- 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.

1 1

[Bug 36146] New: valgrind shows several leaks in dlls/jscript/tests/caller.c
by wine-bugs＠winehq.org June 3, 2014

June 3, 2014

https://bugs.winehq.org/show_bug.cgi?id=36146 Bug ID: 36146 Summary: valgrind shows several leaks in dlls/jscript/tests/caller.c Product: Wine Version: 1.7.17 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: jscript Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==32653== 12 bytes in 1 blocks are definitely lost in loss record 69 of 753 ==32653== at 0x7BC4C6B7: notify_alloc (heap.c:255) ==32653== by 0x7BC50EFB: RtlAllocateHeap (heap.c:1716) ==32653== by 0x697611F: ??? ==32653== by 0x69764DD: ??? ==32653== by 0x6976548: ??? ==32653== by 0x6977213: ??? ==32653== by 0x69793E6: ??? ==32653== by 0x6979560: ??? ==32653== by 0x69796F5: ??? ==32653== by 0x6979D90: ??? ==32653== by 0x6972401: ??? ==32653== by 0x4E4DA12: _call_change_type (dispex.h:686) ==32653== by 0x4E4DC08: test_change_type (caller.c:139) ==32653== by 0x4E4DFD6: test_change_types (caller.c:196) ==32653== by 0x4E4E3B6: test_caller (caller.c:238) ==32653== by 0x4E4EADA: Test_InvokeEx (caller.c:363) ==32653== by 0x695D3E5: ??? ==32653== by 0x69621D9: ??? ==32653== by 0x6966B58: ??? ==32653== by 0x6966F33: ??? ==32653== ==32708== 18 bytes in 1 blocks are definitely lost in loss record 129 of 768 ==32708== at 0x7BC4C6B7: notify_alloc (heap.c:255) ==32708== by 0x7BC50EFB: RtlAllocateHeap (heap.c:1716) ==32708== by 0x6A2F11F: ??? ==32708== by 0x6A2F4DD: ??? ==32708== by 0x6A2F548: ??? ==32708== by 0x6A312DE: ??? ==32708== by 0x6A32C08: ??? ==32708== by 0x6A2B401: ??? ==32708== by 0x4E4E1D2: test_change_types (dispex.h:686) ==32708== by 0x4E4F1E2: run_scripts (caller.c:549) ==32708== by 0x4E4F3CB: func_caller (caller.c:585) ==32708== by 0x4E5ED5F: run_test (test.h:584) ==32708== by 0x4E5F14E: main (test.h:654) ==32708== ==2241== 28 bytes in 1 blocks are definitely lost in loss record 233 of 768 ==2241== at 0x7BC4C6B7: notify_alloc (heap.c:255) ==2241== by 0x7BC50EFB: RtlAllocateHeap (heap.c:1716) ==2241== by 0x6A2F11F: ??? ==2241== by 0x6A2F4DD: ??? ==2241== by 0x6A2F548: ??? ==2241== by 0x6A2F1E3: ??? ==2241== by 0x6A2FE69: ??? ==2241== by 0x6A2BC3E: ??? ==2241== by 0x6A4ABD4: ??? ==2241== by 0x7BC52F48: ??? (loader.c:138) ==2241== by 0x7BC55586: MODULE_InitDLL (loader.c:1068) ==2241== by 0x7BC55904: process_attach (loader.c:1157) ==2241== by 0x7BC5856A: LdrLoadDll (loader.c:2129) ==2241== by 0x7B85A735: load_library (module.c:933) ==2241== by 0x7B85A8A3: LoadLibraryExW (module.c:990) ==2241== by 0x544D69A: COMPOBJ_DllList_Add (compobj.c:495) ==2241== by 0x544FB62: apartment_getclassobject (compobj.c:1335) ==2241== by 0x54532AC: get_inproc_class_object (compobj.c:2894) ==2241== by 0x545376B: CoGetClassObject (compobj.c:3032) ==2241== by 0x5453D2D: CoCreateInstance (compobj.c:3197) Also, possibly: ==2205== 64 bytes in 2 blocks are possibly lost in loss record 411 of 768 ==2205== at 0x7BC4C6B7: notify_alloc (heap.c:255) ==2205== by 0x7BC50EFB: RtlAllocateHeap (heap.c:1716) ==2205== by 0x4FE80B4: alloc_bstr (oleaut.c:162) ==2205== by 0x4FE844A: SysAllocStringLen (oleaut.c:324) ==2205== by 0x4FE8161: SysAllocString (oleaut.c:232) ==2205== by 0x6A15E31: ??? ==2205== by 0x6A1730E: ??? ==2205== by 0x6A174E2: ??? ==2205== by 0x6A17DBF: ??? ==2205== by 0x6A18017: ??? ==2205== by 0x6A18088: ??? ==2205== by 0x6A19957: ??? ==2205== by 0x6A17F2E: ??? ==2205== by 0x6A19D84: ??? ==2205== by 0x6A1A5F8: ??? ==2205== by 0x6A3A6D1: ??? ==2205== by 0x4E4EE13: _parse_script_a (activscp.h:1290) ==2205== by 0x4E4F186: run_scripts (caller.c:541) ==2205== by 0x4E4F3CB: func_caller (caller.c:585) ==2205== by 0x4E5ED5F: run_test (test.h:584) ==2205== -- 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.

1 1

[Bug 36274] New: valgrind shows several leaks in dplayx/tests/dplayx.c
by wine-bugs＠winehq.org June 3, 2014

June 3, 2014

https://bugs.winehq.org/show_bug.cgi?id=36274 Bug ID: 36274 Summary: valgrind shows several leaks in dplayx/tests/dplayx.c Product: Wine Version: 1.7.18 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: directx-dplay Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==7755== 12 bytes in 1 blocks are definitely lost in loss record 65 of 618 ==7755== at 0x7BC4C735: notify_alloc (heap.c:255) ==7755== by 0x7BC50F79: RtlAllocateHeap (heap.c:1716) ==7755== by 0x49DD03C: dplobbysp_create (lobbysp.c:238) ==7755== by 0x49C051A: DP_CreateDirectPlay2 (dplay.c:188) ==7755== by 0x49CFA0E: dplay_create (dplay.c:5708) ==7755== by 0x49BFD87: IClassFactoryImpl_CreateInstance (dpclassfactory.c:87) ==7755== by 0x564DE26: CoCreateInstance (unknwn.h:226) ==7755== by 0x4980A1B: test_COM (dplayx.c:6382) ==7755== by 0x4981932: func_dplayx (dplayx.c:6533) ==7755== by 0x4982818: run_test (test.h:584) ==7755== by 0x4982C06: main (test.h:654) ==7755== ==7755== 24 bytes in 1 blocks are possibly lost in loss record 168 of 618 ==7755== at 0x7BC4C735: notify_alloc (heap.c:255) ==7755== by 0x7BC50F79: RtlAllocateHeap (heap.c:1716) ==7755== by 0x49DDA4E: NS_InitializeSessionCache (name_server.c:263) ==7755== by 0x49C03B3: DP_CreateDirectPlay2 (dplay.c:150) ==7755== by 0x49CFA0E: dplay_create (dplay.c:5708) ==7755== by 0x49BFD87: IClassFactoryImpl_CreateInstance (dpclassfactory.c:87) ==7755== by 0x564DE26: CoCreateInstance (unknwn.h:226) ==7755== by 0x4980A8C: test_COM (dplayx.c:6387) ==7755== by 0x4981932: func_dplayx (dplayx.c:6533) ==7755== by 0x4982818: run_test (test.h:584) ==7755== by 0x4982C06: main (test.h:654) -- 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.

1 2

[Bug 36624] New: valgrind shows uninitialized memory in kernel32/tests/console.c
by wine-bugs＠winehq.org June 3, 2014

June 3, 2014

https://bugs.winehq.org/show_bug.cgi?id=36624 Bug ID: 36624 Summary: valgrind shows uninitialized memory in kernel32/tests/console.c Product: Wine Version: 1.7.19 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com An old valgrind warning that I don't for.. ==18074== Syscall param writev(vector[...]) points to uninitialised byte(s) ==18074== at 0x4E952886: writev (in /usr/lib/libc-2.18.so) ==18074== by 0x7BC7FE6F: send_request (server.c:213) ==18074== by 0x7BC80001: wine_server_call (server.c:294) ==18074== by 0x7B82E0ED: wine_server_call_err (server.h:61) ==18074== by 0x7B82F344: WriteConsoleInputW (console.c:533) ==18074== by 0x4647B58: WCUSER_GenerateMouseInputRecord (user.c:1092) ==18074== by 0x4648005: WCUSER_Proc (user.c:1160) ==18074== by 0x535C5C1: ??? (winproc.c:173) ==18074== by 0x535C736: call_window_proc (winproc.c:244) ==18074== by 0x535E8CF: WINPROC_call_window (winproc.c:900) ==18074== by 0x531FC04: DispatchMessageW (message.c:4019) ==18074== by 0x4648BDF: WCUSER_MainLoop (user.c:1387) ==18074== by 0x464BDA6: WinMain (wineconsole.c:854) ==18074== by 0x464C09F: main (exe_main.c:49) ==18074== Address 0x4d0f74e is on thread 1's stack ==18074== Uninitialised value was created by a stack allocation ==18074== at 0x4647A54: WCUSER_GenerateMouseInputRecord (user.c:1071) ==18074== from http://www.winehq.org/pipermail/wine-devel/2008-November/070539.html: the issue in fixing WCUSER_GenerateMouseInputRecord() is that we'll still get the same warning in valgrind from a partly initialized INPUT_RECORD from any caller to WriteConsoleInput (and the code in wineconsole is perfectly correct as it only assigns the fields it needs for a MouseEvent) the cleanest fix should be in WriteConsoleInput not to pass the undefined parts to wineserver (or to set them to zero) -- 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.

1 1