July 2017 - Wine-bugs - list.winehq.org

[Bug 7284] Max Payne 2 light reflections on people are too bright and blocky
by wine-bugs＠winehq.org 19 Jul '17

19 Jul '17

https://bugs.winehq.org/show_bug.cgi?id=7284 --- Comment #80 from Andrey Gusev <andrey.goosev(a)gmail.com> --- Demo works fine now with wine-2.12-205-g9118512135 and driver 375.66 -- 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 0

[Bug 42321] New: Problems installing Preform, an application that controls a Formlab Form 2 SLA Resin 3D Printer,
by wine-bugs＠winehq.org 19 Jul '17

19 Jul '17

https://bugs.winehq.org/show_bug.cgi?id=42321 Bug ID: 42321 Summary: Problems installing Preform, an application that controls a Formlab Form 2 SLA Resin 3D Printer, Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: richardoakley86(a)gmail.com Distribution: --- The first issue arose when it tried to install Bonjour, after that it had problems with other .dll files. Is this software too specialised for Wine? -- 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 4

[Bug 9424] New: No default item in MDI child sysmenu - cannot close with doubleclick
by wine-bugs＠winehq.org 19 Jul '17

19 Jul '17

http://bugs.winehq.org/show_bug.cgi?id=9424 Summary: No default item in MDI child sysmenu - cannot close with doubleclick Product: Wine Version: CVS/GIT Platform: Other OS/Version: other Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: wine-user AssignedTo: wine-bugs(a)winehq.org ReportedBy: peter(a)cendio.se In Windows, it's possible to close a MDI child window by double clicking the system menu icon. Opening the system icon also shows that Close (ALT-F4) is default, by making it bold. Although the close entry is bold in the latest Wine, it's not possible to close the window by double clicking the system menu icon. A simple test program is available as http://www.cendio.se/~astrand/wine/7-close-dbl-click/mdi1.exe . Verified with the CVS version as of today. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 12

[Bug 41910] New: Endless Legend: black space for water with GLSL enabled, broken resource readouts with disabled
by wine-bugs＠winehq.org 19 Jul '17

19 Jul '17

https://bugs.winehq.org/show_bug.cgi?id=41910 Bug ID: 41910 Summary: Endless Legend: black space for water with GLSL enabled, broken resource readouts with disabled Product: Wine Version: 1.9.24 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: voker57(a)gmail.com Distribution: --- Created attachment 56291 --> https://bugs.winehq.org/attachment.cgi?id=56291 Black water in endless legend With default configuration Endless Legend has black space where water should be, see attachmen. With GLSL disabled (as per this advice https://www.reddit.com/r/wine_gaming/comments/59y4m0/endless_legend_has_bla… ), water is fine and performance is better, but resource readouts are all misplaced. How to reproduce: start new game, find water or click FIDSI button on bottom right for resource readouts -- 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 7

[Bug 36609] New: valgrind shows uninitialized memory use in wscript/tests/run.c
by wine-bugs＠winehq.org 18 Jul '17

18 Jul '17

https://bugs.winehq.org/show_bug.cgi?id=36609 Bug ID: 36609 Summary: valgrind shows uninitialized memory use in wscript/tests/run.c Product: Wine Version: 1.7.19 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: wscript Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==14496== Thread 2: ==14496== Syscall param write(buf) points to uninitialised byte(s) ==14496== at 0x4226D1B: ??? (syscall-template.S:81) ==14496== by 0x7BC46B60: NtWriteFile (file.c:1073) ==14496== by 0x7B83E03E: WriteFile (file.c:563) ==14496== by 0x62C0B3C: rpcrt4_conn_np_write (rpc_transport.c:444) ==14496== by 0x62B5AAB: rpcrt4_conn_write (rpc_binding.h:189) ==14496== by 0x62B7A2D: RPCRT4_SendWithAuth (rpc_message.c:849) ==14496== by 0x62B8B24: RPCRT4_Send (rpc_message.c:1245) ==14496== by 0x62BA3B1: I_RpcSend (rpc_message.c:1806) ==14496== by 0x62BA73B: I_RpcSendReceive (rpc_message.c:1909) ==14496== by 0x5F6DA45: rpc_sendreceive_thread (rpc.c:801) ==14496== by 0x7BC90A24: worker_thread_proc (threadpool.c:110) ==14496== by 0x7BC870C7: ??? (signal_i386.c:2571) ==14496== by 0x7BC87110: call_thread_func (signal_i386.c:2630) ==14496== by 0x7BC870A5: ??? (signal_i386.c:2571) ==14496== by 0x7BC8E4EC: start_thread (thread.c:428) ==14496== by 0x421FF92: start_thread (pthread_create.c:309) ==14496== by 0x43247ED: clone (clone.S:129) ==14496== Address 0x49a4c32 is 138 bytes inside a block of size 256 alloc'd ==14496== at 0x7BC4C6DF: notify_alloc (heap.c:255) ==14496== by 0x7BC50F23: RtlAllocateHeap (heap.c:1716) ==14496== by 0x62B786D: RPCRT4_SendWithAuth (rpc_message.c:808) ==14496== by 0x62B8B24: RPCRT4_Send (rpc_message.c:1245) ==14496== by 0x62BA3B1: I_RpcSend (rpc_message.c:1806) ==14496== by 0x62BA73B: I_RpcSendReceive (rpc_message.c:1909) ==14496== by 0x5F6DA45: rpc_sendreceive_thread (rpc.c:801) ==14496== by 0x7BC90A24: worker_thread_proc (threadpool.c:110) ==14496== by 0x7BC870C7: ??? (signal_i386.c:2571) ==14496== by 0x7BC87110: call_thread_func (signal_i386.c:2630) ==14496== by 0x7BC870A5: ??? (signal_i386.c:2571) ==14496== by 0x7BC8E4EC: start_thread (thread.c:428) ==14496== by 0x421FF92: start_thread (pthread_create.c:309) ==14496== by 0x43247ED: clone (clone.S:129) ==14496== Uninitialised value was created by a stack allocation ==14496== at 0x6A5D0C9: disp_call (dispex.c:1096) ==14496== -- 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 43388] New: valgrind shows a few definite leaks in dlls/winmm/tests/ mci.c
by wine-bugs＠winehq.org 18 Jul '17

18 Jul '17

https://bugs.winehq.org/show_bug.cgi?id=43388 Bug ID: 43388 Summary: valgrind shows a few definite leaks in dlls/winmm/tests/mci.c Product: Wine Version: 2.12 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase, valgrind Severity: normal Priority: P2 Component: winmm&mci Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: Gentoo ==2739== 0 bytes in 1 blocks are definitely lost in loss record 6 of 1,022 ==2739== at 0x7BC51061: notify_alloc (heap.c:254) ==2739== by 0x7BC5554F: RtlAllocateHeap (heap.c:1716) ==2739== by 0x523E42B: IMalloc_fnAlloc (ifs.c:187) ==2739== by 0x523ECCB: IMalloc_Alloc (objidl.h:1405) ==2739== by 0x523ECCB: CoTaskMemAlloc (???:0) ==2739== by 0x1A4983D5: ??? ==2739== by 0x1A49D191: ??? ==2739== by 0x1A49D275: ??? ==2739== by 0x1A49D767: ??? ==2739== by 0x1A49DC76: ??? ==2739== by 0x19B3BF99: ??? ==2739== by 0x7BC913B3: ??? (signal_i386.c:2700) ==2739== by 0x7BC9143B: call_thread_func (signal_i386.c:2759) ==2739== by 0x7BC91391: ??? (signal_i386.c:2700) ==2739== by 0x7BC9B3EE: start_thread (thread.c:487) ==2739== by 0x4244249: start_thread (pthread_create.c:333) ==2739== by 0x433FD6D: clone (clone.S:114) ==2739== ==2739== 0 bytes in 1 blocks are definitely lost in loss record 7 of 1,022 ==2739== at 0x7BC51061: notify_alloc (heap.c:254) ==2739== by 0x7BC5554F: RtlAllocateHeap (heap.c:1716) ==2739== by 0x523E42B: IMalloc_fnAlloc (ifs.c:187) ==2739== by 0x523ECCB: IMalloc_Alloc (objidl.h:1405) ==2739== by 0x523ECCB: CoTaskMemAlloc (???:0) ==2739== by 0x1A4983D5: ??? ==2739== by 0x1A49D191: ??? ==2739== by 0x1A49D275: ??? ==2739== by 0x1A49D767: ??? ==2739== by 0x1A49DC8D: ??? ==2739== by 0x19B3BF99: ??? ==2739== by 0x7BC913B3: ??? (signal_i386.c:2700) ==2739== by 0x7BC9143B: call_thread_func (signal_i386.c:2759) ==2739== by 0x7BC91391: ??? (signal_i386.c:2700) ==2739== by 0x7BC9B3EE: start_thread (thread.c:487) ==2739== by 0x4244249: start_thread (pthread_create.c:333) ==2739== by 0x433FD6D: clone (clone.S:114) ==2739== ==2739== 0 bytes in 1 blocks are definitely lost in loss record 12 of 1,022 ==2739== at 0x7BC51061: notify_alloc (heap.c:254) ==2739== by 0x7BC5554F: RtlAllocateHeap (heap.c:1716) ==2739== by 0x523E42B: IMalloc_fnAlloc (ifs.c:187) ==2739== by 0x523ECCB: IMalloc_Alloc (objidl.h:1405) ==2739== by 0x523ECCB: CoTaskMemAlloc (???:0) ==2739== by 0x1A4983D5: ??? ==2739== by 0x1A49D191: ??? ==2739== by 0x1A49D275: ??? ==2739== by 0x1A49D767: ??? ==2739== by 0x1A49DC76: ??? ==2739== by 0x19C52F99: ??? ==2739== by 0x7BC913B3: ??? (signal_i386.c:2700) ==2739== by 0x7BC9143B: call_thread_func (signal_i386.c:2759) ==2739== by 0x7BC91391: ??? (signal_i386.c:2700) ==2739== by 0x7BC9B3EE: start_thread (thread.c:487) ==2739== by 0x4244249: start_thread (pthread_create.c:333) ==2739== by 0x433FD6D: clone (clone.S:114) ==2739== ==2739== 0 bytes in 2 blocks are definitely lost in loss record 13 of 1,022 ==2739== at 0x7BC51061: notify_alloc (heap.c:254) ==2739== by 0x7BC5554F: RtlAllocateHeap (heap.c:1716) ==2739== by 0x523E42B: IMalloc_fnAlloc (ifs.c:187) ==2739== by 0x523ECCB: IMalloc_Alloc (objidl.h:1405) ==2739== by 0x523ECCB: CoTaskMemAlloc (???:0) ==2739== by 0x1A4983D5: ??? ==2739== by 0x1A49D191: ??? ==2739== by 0x1A49D275: ??? ==2739== by 0x1A49D767: ??? ==2739== by 0x1A49DC8D: ??? ==2739== by 0x19C52F99: ??? ==2739== by 0x7BC913B3: ??? (signal_i386.c:2700) ==2739== by 0x7BC9143B: call_thread_func (signal_i386.c:2759) ==2739== by 0x7BC91391: ??? (signal_i386.c:2700) ==2739== by 0x7BC9B3EE: start_thread (thread.c:487) ==2739== by 0x4244249: start_thread (pthread_create.c:333) ==2739== by 0x433FD6D: clone (clone.S:114) ==2739== -- 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 0

[Bug 36581] New: valgrind shows a few leaks in winmm/tests/capture.c
by wine-bugs＠winehq.org 18 Jul '17

18 Jul '17

https://bugs.winehq.org/show_bug.cgi?id=36581 Bug ID: 36581 Summary: valgrind shows a few leaks in winmm/tests/capture.c Product: Wine Version: 1.7.19 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: winmm&mci Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com austin(a)aw25 ~/wine-valgrind/dlls/winmm/tests $ make capture.ok ../../../tools/runtest -q -P wine -T ../../.. -M winmm.dll -p winmm_test.exe.so capture && touch capture.ok preloader: Warning: failed to reserve range 00110000-68000000 preloader: Warning: failed to reserve range 7f000000-82000000 ==26292== 512 bytes in 1 blocks are definitely lost in loss record 665 of 832 ==26292== at 0x7BC4C6DF: notify_alloc (heap.c:255) ==26292== by 0x7BC50F23: RtlAllocateHeap (heap.c:1716) ==26292== by 0x5126CA4: list_window_children (win.c:318) ==26292== by 0x512EE26: WIN_ListChildren (win.c:3267) ==26292== by 0x512B3BC: WIN_SendDestroyMsg (win.c:1783) ==26292== by 0x512B7F5: DestroyWindow (win.c:1876) ==26292== by 0x4FDF40A: WINMM_DevicesThreadDone (waveform.c:2445) ==26292== by 0x4FDF896: WINMM_DevicesThreadProc (waveform.c:2516) ==26292== by 0x7BC870C7: ??? (signal_i386.c:2571) ==26292== by 0x7BC87110: call_thread_func (signal_i386.c:2630) ==26292== by 0x7BC870A5: ??? (signal_i386.c:2571) ==26292== by 0x7BC8E4EC: start_thread (thread.c:428) ==26292== by 0x421FF92: start_thread (pthread_create.c:309) ==26292== by 0x43247ED: clone (clone.S:129) ==26292== ==26292== 5,940 bytes in 330 blocks are definitely lost in loss record 818 of 832 ==26292== at 0x7BC4C6DF: notify_alloc (heap.c:255) ==26292== by 0x7BC50F23: RtlAllocateHeap (heap.c:1716) ==26292== by 0x4FDACEF: WINMM_OpenDevice (waveform.c:1093) ==26292== by 0x4FDBCAB: WID_Open (waveform.c:1361) ==26292== by 0x4FDF30B: WINMM_DevicesMsgProc (waveform.c:2413) ==26292== by 0x51394F5: ??? (winproc.c:173) ==26292== by 0x513966A: call_window_proc (winproc.c:244) ==26292== by 0x513B803: WINPROC_call_window (winproc.c:900) ==26292== by 0x50F811C: call_window_proc (message.c:2223) ==26292== by 0x50FA320: peek_message (message.c:2953) ==26292== by 0x50FBDC6: PeekMessageW (message.c:3757) ==26292== by 0x4FDF773: WINMM_DevicesThreadProc (waveform.c:2503) ==26292== by 0x7BC870C7: ??? (signal_i386.c:2571) ==26292== by 0x7BC87110: call_thread_func (signal_i386.c:2630) ==26292== by 0x7BC870A5: ??? (signal_i386.c:2571) ==26292== by 0x7BC8E4EC: start_thread (thread.c:428) ==26292== by 0x421FF92: start_thread (pthread_create.c:309) ==26292== by 0x43247ED: clone (clone.S:129) ==26292== -- 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 3

[Bug 36638] New: valgrind shows a definite leak in wininet/tests/http.c
by wine-bugs＠winehq.org 18 Jul '17

18 Jul '17

https://bugs.winehq.org/show_bug.cgi?id=36638 Bug ID: 36638 Summary: valgrind shows a definite leak in wininet/tests/http.c Product: Wine Version: 1.7.19 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: wininet Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Depends on: 36637 ==32063== Thread 1 wininet_test.exe.so: ==32063== 32 bytes in 1 blocks are definitely lost in loss record 111 of 360 ==32063== at 0x7BC4C75D: notify_alloc (heap.c:255) ==32063== by 0x7BC50FA1: RtlAllocateHeap (heap.c:1716) ==32063== by 0x4D45FA1: heap_alloc (internet.h:116) ==32063== by 0x4D4FE13: alloc_async_task (internet.c:3856) ==32063== by 0x4D44055: HttpSendRequestW (http.c:5556) ==32063== by 0x4D44251: HttpSendRequestA (http.c:5614) ==32063== by 0x497CC63: test_InternetCloseHandle (http.c:5195) ==32063== by 0x497D671: func_http (http.c:5328) ==32063== by 0x4994B90: run_test (test.h:584) ==32063== by 0x4994F7F: main (test.h:654) ==32063== -- 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 4

[Bug 36578] New: valgrind shows several definite leaks in urlmon/tests/url.c
by wine-bugs＠winehq.org 18 Jul '17

18 Jul '17

https://bugs.winehq.org/show_bug.cgi?id=36578 Bug ID: 36578 Summary: valgrind shows several definite leaks in urlmon/tests/url.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 ==23547== 8 bytes in 1 blocks are definitely lost in loss record 384 of 6,179 ==23547== at 0x7BC4C6DF: notify_alloc (heap.c:255) ==23547== by 0x7BC50F23: RtlAllocateHeap (heap.c:1716) ==23547== by 0x8C3E633: SECUR32_makeSecHandle (wrapper.c:44) ==23547== by 0x8C3F148: InitializeSecurityContextW (wrapper.c:354) ==23547== by 0x65D180A: netcon_secure_connect_setup (netconnection.c:538) ==23547== by 0x65D2170: NETCON_secure_connect (netconnection.c:686) ==23547== by 0x65C048F: HTTP_HttpSendRequestW (http.c:4925) ==23547== by 0x65C11FA: AsyncHttpSendRequestProc (http.c:5182) ==23547== by 0x65CDD83: INTERNET_WorkerThreadFunc (internet.c:3840) ==23547== by 0x7BC90A24: worker_thread_proc (threadpool.c:110) ==23547== by 0x7BC870C7: ??? (signal_i386.c:2571) ==23547== by 0x7BC87110: call_thread_func (signal_i386.c:2630) ==23547== by 0x7BC870A5: ??? (signal_i386.c:2571) ==23547== by 0x7BC8E4EC: start_thread (thread.c:428) ==23547== by 0x421FF92: start_thread (pthread_create.c:309) ==23547== by 0x43247ED: clone (clone.S:129) ==23547== ==5217== 20 bytes in 1 blocks are definitely lost in loss record 1,185 of 6,082 ==5217== at 0x7BC4C6DF: notify_alloc (heap.c:255) ==5217== by 0x7BC50F23: RtlAllocateHeap (heap.c:1716) ==5217== by 0x4EBFBC7: heap_alloc (urlmon_main.h:236) ==5217== by 0x4EC1915: create_moniker (umon.c:545) ==5217== by 0x4EC1CCE: CreateURLMonikerEx (umon.c:656) ==5217== by 0x4EC1FC3: CreateURLMoniker (umon.c:734) ==5217== by 0x4CFE492: test_BindToStorage (url.c:2915) ==5217== by 0x4D05327: func_url (url.c:4077) ==5217== by 0x4D06166: run_test (test.h:584) ==5217== by 0x4D06555: main (test.h:654) ==5217== ==5217== 36 bytes in 1 blocks are possibly lost in loss record 2,510 of 6,082 ==5217== at 0x7BC4C6DF: notify_alloc (heap.c:255) ==5217== by 0x7BC50F23: RtlAllocateHeap (heap.c:1716) ==5217== by 0x4EBD59D: heap_alloc (urlmon_main.h:236) ==5217== by 0x4EBDB3C: register_namespace (session.c:126) ==5217== by 0x4EBE832: InternetSession_RegisterNameSpace (session.c:375) ==5217== by 0x4D0417D: register_protocols (urlmon.h:3759) ==5217== by 0x4D0432A: func_url (url.c:3865) ==5217== by 0x4D06166: run_test (test.h:584) ==5217== by 0x4D06555: main (test.h:654) ==5217== -- 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 3

[Bug 43386] New: valgrind shows uninitialized memory in dlls/shell32/tests /shelldispatch.c
by wine-bugs＠winehq.org 18 Jul '17

18 Jul '17

https://bugs.winehq.org/show_bug.cgi?id=43386 Bug ID: 43386 Summary: valgrind shows uninitialized memory in dlls/shell32/tests/shelldispatch.c Product: Wine Version: 2.12 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase, valgrind Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: Gentoo ==368== Thread 3: ==368== Syscall param writev(vector[...]) points to uninitialised byte(s) ==368== at 0x433804F: ??? (syscall-template.S:84) ==368== by 0x7BC8946B: send_request (server.c:228) ==368== by 0x7BC89626: wine_server_call (server.c:309) ==368== by 0x7BC4867A: server_write_file (file.c:624) ==368== by 0x7BC49E71: NtWriteFile (file.c:1238) ==368== by 0x5969332: rpcrt4_conn_np_write (rpc_transport.c:414) ==368== by 0x595E242: rpcrt4_conn_write (rpc_binding.h:196) ==368== by 0x5960001: RPCRT4_SendWithAuth (rpc_message.c:849) ==368== by 0x5961050: RPCRT4_Send (rpc_message.c:1248) ==368== by 0x59627D4: I_RpcSend (rpc_message.c:1809) ==368== by 0x5962B49: I_RpcSendReceive (rpc_message.c:1912) ==368== by 0x55E1881: rpc_sendreceive_thread (rpc.c:800) ==368== by 0x7BC9E2D7: process_rtl_work_item (threadpool.c:349) ==368== by 0x7BCA2224: threadpool_worker_proc (threadpool.c:2112) ==368== by 0x7BC913B3: ??? (signal_i386.c:2700) ==368== by 0x7BC9143B: call_thread_func (signal_i386.c:2759) ==368== by 0x7BC91391: ??? (signal_i386.c:2700) ==368== by 0x7BC9B3EE: start_thread (thread.c:487) ==368== by 0x4244249: start_thread (pthread_create.c:333) ==368== by 0x433FD6D: clone (clone.S:114) ==368== Address 0x667ec72 is 90 bytes inside a recently re-allocated block of size 140 alloc'd ==368== at 0x7BC51061: notify_alloc (heap.c:254) ==368== by 0x7BC5554F: RtlAllocateHeap (heap.c:1716) ==368== by 0x595FE79: RPCRT4_SendWithAuth (rpc_message.c:808) ==368== by 0x5961050: RPCRT4_Send (rpc_message.c:1248) ==368== by 0x59627D4: I_RpcSend (rpc_message.c:1809) ==368== by 0x5962B49: I_RpcSendReceive (rpc_message.c:1912) ==368== by 0x55E1881: rpc_sendreceive_thread (rpc.c:800) ==368== by 0x7BC9E2D7: process_rtl_work_item (threadpool.c:349) ==368== by 0x7BCA2224: threadpool_worker_proc (threadpool.c:2112) ==368== by 0x7BC913B3: ??? (signal_i386.c:2700) ==368== by 0x7BC9143B: call_thread_func (signal_i386.c:2759) ==368== by 0x7BC91391: ??? (signal_i386.c:2700) ==368== by 0x7BC9B3EE: start_thread (thread.c:487) ==368== by 0x4244249: start_thread (pthread_create.c:333) ==368== by 0x433FD6D: clone (clone.S:114) ==368== Uninitialised value was created by a stack allocation ==368== at 0x4A30CB3: test_ShellWindows (shelldispatch.c:679) ==368== -- 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 0