vex x86->IR: unhandled instruction bytes: 0xFB 0xC3 0x0 0x0 valgrind: Unrecognised instruction at address 0x7f230000. Your program just tried to execute an instruction that Valgrind did not recognise. There are two possible reasons for this. 1. Your program has a bug and erroneously jumped to a non-code location. If you are running Memcheck and you just saw a warning about a bad jump, it's probably your program's fault. 2. The instruction is legitimate but Valgrind doesn't handle it, i.e. it's Valgrind's fault. If you think this is the case or you are not sure, please let us know and we'll try to fix it. Either way, Valgrind will now raise a SIGILL signal which will probably kill your program. err:seh:segv_handler Got unexpected trap 0 exception.c:371: Test failed: 0: Wrong exception code c000001d/c0000096 valgrind: Unrecognised instruction at address 0x7f230000. Your program just tried to execute an instruction that Valgrind did not recognise. There are two possible reasons for this. 1. Your program has a bug and erroneously jumped to a non-code location. If you are running Memcheck and you just saw a warning about a bad jump, it's probably your program's fault. 2. The instruction is legitimate but Valgrind doesn't handle it, i.e. it's Valgrind's fault. If you think this is the case or you are not sure, please let us know and we'll try to fix it. Either way, Valgrind will now raise a SIGILL signal which will probably kill your program. err:seh:segv_handler Got unexpected trap 0 exception.c:371: Test failed: 1: Wrong exception code c000001d/c0000096 valgrind: Unrecognised instruction at address 0x7f230000. Your program just tried to execute an instruction that Valgrind did not recognise. There are two possible reasons for this. 1. Your program has a bug and erroneously jumped to a non-code location. If you are running Memcheck and you just saw a warning about a bad jump, it's probably your program's fault. 2. The instruction is legitimate but Valgrind doesn't handle it, i.e. it's Valgrind's fault. If you think this is the case or you are not sure, please let us know and we'll try to fix it. Either way, Valgrind will now raise a SIGILL signal which will probably kill your program. err:seh:segv_handler Got unexpected trap 0 exception.c:371: Test failed: 2: Wrong exception code c000001d/c0000096 valgrind: Unrecognised instruction at address 0x7f230000. Your program just tried to execute an instruction that Valgrind did not recognise. There are two possible reasons for this. 1. Your program has a bug and erroneously jumped to a non-code location. If you are running Memcheck and you just saw a warning about a bad jump, it's probably your program's fault. 2. The instruction is legitimate but Valgrind doesn't handle it, i.e. it's Valgrind's fault. If you think this is the case or you are not sure, please let us know and we'll try to fix it. Either way, Valgrind will now raise a SIGILL signal which will probably kill your program. err:seh:segv_handler Got unexpected trap 0 exception.c:371: Test failed: 3: Wrong exception code c000001d/c0000096 valgrind: Unrecognised instruction at address 0x7f230000. Your program just tried to execute an instruction that Valgrind did not recognise. There are two possible reasons for this. 1. Your program has a bug and erroneously jumped to a non-code location. If you are running Memcheck and you just saw a warning about a bad jump, it's probably your program's fault. 2. The instruction is legitimate but Valgrind doesn't handle it, i.e. it's Valgrind's fault. If you think this is the case or you are not sure, please let us know and we'll try to fix it. Either way, Valgrind will now raise a SIGILL signal which will probably kill your program. err:seh:segv_handler Got unexpected trap 0 exception.c:371: Test failed: 4: Wrong exception code c000001d/c0000096 valgrind: Unrecognised instruction at address 0x7f230000. Your program just tried to execute an instruction that Valgrind did not recognise. There are two possible reasons for this. 1. Your program has a bug and erroneously jumped to a non-code location. If you are running Memcheck and you just saw a warning about a bad jump, it's probably your program's fault. 2. The instruction is legitimate but Valgrind doesn't handle it, i.e. it's Valgrind's fault. If you think this is the case or you are not sure, please let us know and we'll try to fix it. Either way, Valgrind will now raise a SIGILL signal which will probably kill your program. err:seh:segv_handler Got unexpected trap 0 exception.c:371: Test failed: 5: Wrong exception code c000001d/c0000096 valgrind: Unrecognised instruction at address 0x7f230000. Your program just tried to execute an instruction that Valgrind did not recognise. There are two possible reasons for this. 1. Your program has a bug and erroneously jumped to a non-code location. If you are running Memcheck and you just saw a warning about a bad jump, it's probably your program's fault. 2. The instruction is legitimate but Valgrind doesn't handle it, i.e. it's Valgrind's fault. If you think this is the case or you are not sure, please let us know and we'll try to fix it. Either way, Valgrind will now raise a SIGILL signal which will probably kill your program. err:seh:segv_handler Got unexpected trap 0 exception.c:371: Test failed: 6: Wrong exception code c000001d/c0000096 valgrind: Unrecognised instruction at address 0x7f230000. Your program just tried to execute an instruction that Valgrind did not recognise. There are two possible reasons for this. 1. Your program has a bug and erroneously jumped to a non-code location. If you are running Memcheck and you just saw a warning about a bad jump, it's probably your program's fault. 2. The instruction is legitimate but Valgrind doesn't handle it, i.e. it's Valgrind's fault. If you think this is the case or you are not sure, please let us know and we'll try to fix it. Either way, Valgrind will now raise a SIGILL signal which will probably kill your program. err:seh:segv_handler Got unexpected trap 0 exception.c:371: Test failed: 7: Wrong exception code c000001d/c0000096 valgrind: Unrecognised instruction at address 0x7f230000. Your program just tried to execute an instruction that Valgrind did not recognise. There are two possible reasons for this. 1. Your program has a bug and erroneously jumped to a non-code location. If you are running Memcheck and you just saw a warning about a bad jump, it's probably your program's fault. 2. The instruction is legitimate but Valgrind doesn't handle it, i.e. it's Valgrind's fault. If you think this is the case or you are not sure, please let us know and we'll try to fix it. Either way, Valgrind will now raise a SIGILL signal which will probably kill your program. err:seh:segv_handler Got unexpected trap 0 exception.c:371: Test failed: 8: Wrong exception code c000001d/c0000096 valgrind: Unrecognised instruction at address 0x7f230000. Your program just tried to execute an instruction that Valgrind did not recognise. There are two possible reasons for this. 1. Your program has a bug and erroneously jumped to a non-code location. If you are running Memcheck and you just saw a warning about a bad jump, it's probably your program's fault. 2. The instruction is legitimate but Valgrind doesn't handle it, i.e. it's Valgrind's fault. If you think this is the case or you are not sure, please let us know and we'll try to fix it. Either way, Valgrind will now raise a SIGILL signal which will probably kill your program. err:seh:segv_handler Got unexpected trap 0 exception.c:371: Test failed: 9: Wrong exception code c000001d/c0000096 valgrind: Unrecognised instruction at address 0x7f230000. Your program just tried to execute an instruction that Valgrind did not recognise. There are two possible reasons for this. 1. Your program has a bug and erroneously jumped to a non-code location. If you are running Memcheck and you just saw a warning about a bad jump, it's probably your program's fault. 2. The instruction is legitimate but Valgrind doesn't handle it, i.e. it's Valgrind's fault. If you think this is the case or you are not sure, please let us know and we'll try to fix it. Either way, Valgrind will now raise a SIGILL signal which will probably kill your program. err:seh:segv_handler Got unexpected trap 0 exception.c:371: Test failed: 10: Wrong exception code c000001d/c0000096 valgrind: Unrecognised instruction at address 0x7f230000. Your program just tried to execute an instruction that Valgrind did not recognise. There are two possible reasons for this. 1. Your program has a bug and erroneously jumped to a non-code location. If you are running Memcheck and you just saw a warning about a bad jump, it's probably your program's fault. 2. The instruction is legitimate but Valgrind doesn't handle it, i.e. it's Valgrind's fault. If you think this is the case or you are not sure, please let us know and we'll try to fix it. Either way, Valgrind will now raise a SIGILL signal which will probably kill your program. err:seh:segv_handler Got unexpected trap 0 exception.c:371: Test failed: 11: Wrong exception code c000001d/c0000096 valgrind: Unrecognised instruction at address 0x7f230000. Your program just tried to execute an instruction that Valgrind did not recognise. There are two possible reasons for this. 1. Your program has a bug and erroneously jumped to a non-code location. If you are running Memcheck and you just saw a warning about a bad jump, it's probably your program's fault. 2. The instruction is legitimate but Valgrind doesn't handle it, i.e. it's Valgrind's fault. If you think this is the case or you are not sure, please let us know and we'll try to fix it. Either way, Valgrind will now raise a SIGILL signal which will probably kill your program. err:seh:segv_handler Got unexpected trap 0 exception.c:371: Test failed: 12: Wrong exception code c000001d/c0000096 valgrind: Unrecognised instruction at address 0x7f230000. Your program just tried to execute an instruction that Valgrind did not recognise. There are two possible reasons for this. 1. Your program has a bug and erroneously jumped to a non-code location. If you are running Memcheck and you just saw a warning about a bad jump, it's probably your program's fault. 2. The instruction is legitimate but Valgrind doesn't handle it, i.e. it's Valgrind's fault. If you think this is the case or you are not sure, please let us know and we'll try to fix it. Either way, Valgrind will now raise a SIGILL signal which will probably kill your program. err:seh:segv_handler Got unexpected trap 0 exception.c:371: Test failed: 13: Wrong exception code c000001d/c0000096 valgrind: Unrecognised instruction at address 0x7f230000. Your program just tried to execute an instruction that Valgrind did not recognise. There are two possible reasons for this. 1. Your program has a bug and erroneously jumped to a non-code location. If you are running Memcheck and you just saw a warning about a bad jump, it's probably your program's fault. 2. The instruction is legitimate but Valgrind doesn't handle it, i.e. it's Valgrind's fault. If you think this is the case or you are not sure, please let us know and we'll try to fix it. Either way, Valgrind will now raise a SIGILL signal which will probably kill your program. err:seh:segv_handler Got unexpected trap 0 exception.c:371: Test failed: 14: Wrong exception code c000001d/c0000005 exception.c:377: Test failed: 14: Wrong number of parameters 0/2 Conditional jump or move depends on uninitialised value(s) at handler (exception.c:384) by ??? (signal_i386.c:2478) by ??? (signal_i386.c:2478) by call_stack_handlers (signal_i386.c:606) by raise_exception (signal_i386.c:684) by NtRaiseException (signal_i386.c:2376) by raise_segv_exception (signal_i386.c:1709) by ??? by test_prot_fault (exception.c:416) by func_exception (exception.c:1432) by run_test (test.h:541) by main (test.h:591) Uninitialised value was created by a client request at setup_exception_record (signal_i386.c:1587) by segv_handler (signal_i386.c:1834) by ??? (in /lib/tls/i686/cmov/libpthread-2.10.1.so) { Memcheck:Cond fun:handler obj:/home/dank/wine-git/dlls/ntdll/ntdll.dll.so obj:/home/dank/wine-git/dlls/ntdll/ntdll.dll.so fun:call_stack_handlers fun:raise_exception fun:NtRaiseException fun:raise_segv_exception obj:* fun:test_prot_fault fun:func_exception fun:run_test fun:main } valgrind: Unrecognised instruction at address 0x7f230000. Your program just tried to execute an instruction that Valgrind did not recognise. There are two possible reasons for this. 1. Your program has a bug and erroneously jumped to a non-code location. If you are running Memcheck and you just saw a warning about a bad jump, it's probably your program's fault. 2. The instruction is legitimate but Valgrind doesn't handle it, i.e. it's Valgrind's fault. If you think this is the case or you are not sure, please let us know and we'll try to fix it. Either way, Valgrind will now raise a SIGILL signal which will probably kill your program. err:seh:segv_handler Got unexpected trap 0 exception.c:371: Test failed: 15: Wrong exception code c000001d/c0000005 exception.c:373: Test failed: 15: Wrong exception address 0x7f230000/0x7f230006 exception.c:377: Test failed: 15: Wrong number of parameters 0/2 wine: Unhandled illegal instruction at address 0x7f230000 (thread 003e), starting debugger... Memcheck, a memory error detector Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al. Using Valgrind-3.6.0.SVN and LibVEX; rerun with -h for copyright info Command: /home/dank/wine-git/loader/wine-preloader /home/dank/wine-git/loader/wine winedbg --auto 34 48 preloader: Warning: failed to reserve range 00110000-68000000 Unhandled exception: illegal instruction in 32-bit code (0x7f230000). Register dump: CS:0073 SS:007b DS:007b ES:0000 FS:000b GS:0013 EIP:7f230000 ESP:7f22fc7c EBP:7f22fcb8 EFLAGS:00000044( - -- Z- -P- ) EAX:7f230000 EBX:049aaff4 ECX:04994735 EDX:7f22fc98 ESI:7f22fe70 EDI:00000000 Stack dump: 0x7f22fc7c: 0495a50a 7f230000 04994734 00000012 0x7f22fc8c: 0498c6d2 00000001 04994e4f 7f22ff08 0x7f22fc9c: 0495abeb 04994734 00000040 7f22fcc8 0x7f22fcac: 7f230000 7f002290 049aaff4 7f22fcf8 0x7f22fcbc: 0495af5b 0495abeb 04994734 04994734 0x7f22fccc: 00000012 00000000 7f22fce0 00000000 Backtrace: =>0 0x7f230000 (0x7f22fcb8) 1 0x0495af5b test_prot_fault+0x6b() [/home/dank/wine-git/dlls/ntdll/tests/exception.c:418] in ntdll_test (0x7f22fcf8) 2 0x0495d568 func_exception+0x38e() [/home/dank/wine-git/dlls/ntdll/tests/exception.c:1433] in ntdll_test (0x7f22fd28) 3 0x0498ced4 run_test+0x9f(name="exception.c") [/home/dank/wine-git/dlls/ntdll/tests/../../../include/wine/test.h:543] in ntdll_test (0x7f22fd88) 4 0x0498d1ee main+0x1f1(argc=0x7f22fe70, argv=0x7f001cf8) [/home/dank/wine-git/dlls/ntdll/tests/../../../include/wine/test.h:592] in ntdll_test (0x7f22fe58) 5 0x0498d27e __wine_spec_exe_entry+0x6a(peb=0x7ffdf000) [/home/dank/wine-git/dlls/winecrt0/exe_entry.c:36] in ntdll_test (0x7f22fe98) 6 0x04854ba4 start_process+0x137(peb=0x7ffdf000) [/home/dank/wine-git/dlls/kernel32/process.c:1028] in kernel32 (0x7f22fed8) 7 0x047569f0 call_thread_func+0xc() in ntdll (0x7f22fee8) 8 0x04756a2e call_thread_entry_point+0x34(entry=0x4854a6d, arg=0x7ffdf000) [/home/dank/wine-git/dlls/ntdll/signal_i386.c:2457] in ntdll (0x7f22ffc8) 9 0x0472f736 LdrInitializeThunk(kernel_start=0x7ffdf000, unknown2=0, unknown3=0, unknown4=0) [/home/dank/wine-git/dlls/ntdll/loader.c:2621] in ntdll (0x7f22ffe8) 0x7f230000: pushl $0x0 Modules: Module Address Debug info Name (50 modules) ELF 4000000- 401d000 Deferred ld-linux.so.2 ELF 401f000- 4022000 Deferred vgpreload_core-x86-linux.so ELF 4022000- 402a000 Deferred vgpreload_memcheck-x86-linux.so ELF 402a000- 4167000 Deferred libwine.so.1 ELF 4178000- 4191000 Deferred libpthread.so.0 ELF 4192000- 42d7000 Deferred libc.so.6 ELF 42d7000- 42db000 Deferred libdl.so.2 ELF 46dc000- 479d000 Dwarf ntdll \-PE 46f0000- 479d000 \ ntdll ELF 479d000- 47c3000 Deferred libm.so.6 ELF 47c3000- 47cb000 Deferred libnss_compat.so.2 ELF 47cb000- 47e2000 Deferred libnsl.so.1 ELF 47e2000- 47ed000 Deferred libnss_nis.so.2 ELF 47ed000- 47f9000 Deferred libnss_files.so.2 ELF 47f9000- 4938000 Dwarf kernel32 \-PE 4810000- 4938000 \ kernel32 ELF 4938000- 49ad000 Dwarf ntdll_test \-PE 4940000- 49ad000 \ ntdll_test ELF 49ad000- 4acf000 Deferred user32 \-PE 49c0000- 4acf000 \ user32 ELF 4acf000- 4b69000 Deferred gdi32 \-PE 4ae0000- 4b69000 \ gdi32 ELF 4b69000- 4bc5000 Deferred advapi32 \-PE 4b80000- 4bc5000 \ advapi32 ELF 4bc5000- 4c3e000 Deferred rpcrt4 \-PE 4bd0000- 4c3e000 \ rpcrt4 ELF 4c3e000- 4cbd000 Deferred libfreetype.so.6 ELF 4cbd000- 4cd3000 Deferred libz.so.1 ELF 4cd3000- 4d00000 Deferred libfontconfig.so.1 ELF 4d00000- 4d27000 Deferred libexpat.so.1 ELF 4d49000- 4dfa000 Deferred winex11 \-PE 4d60000- 4dfa000 \ winex11 ELF 4e0b000- 4e14000 Deferred libsm.so.6 ELF 4e14000- 4e2f000 Deferred libice.so.6 ELF 4e2f000- 4e3f000 Deferred libxext.so.6 ELF 4e3f000- 4f6e000 Deferred libx11.so.6 ELF 4f6e000- 4f73000 Deferred libuuid.so.1 ELF 4f73000- 4f77000 Deferred libxau.so.6 ELF 4f77000- 4f95000 Deferred libxcb.so.1 ELF 4f95000- 4f9a000 Deferred libxdmcp.so.6 ELF 4f9a000- 4fbb000 Deferred imm32 \-PE 4fa0000- 4fbb000 \ imm32 ELF 4fbb000- 4fbe000 Deferred libxinerama.so.1 ELF 4fbe000- 4fc4000 Deferred libxxf86vm.so.1 ELF 4fc4000- 4fce000 Deferred libxrender.so.1 ELF 4fce000- 4fd7000 Deferred libxrandr.so.2 ELF 4fd7000- 4fdb000 Deferred libxcomposite.so.1 ELF 4fdb000- 4fe1000 Deferred libxfixes.so.3 ELF 4fe1000- 4fec000 Deferred libxcursor.so.1 ELF 7bf00000-7bf04000 Deferred Threads: process tid prio (all id:s are in hex) 00000008 notepad.exe 00000009 0 0000000e services.exe 00000014 0 00000010 0 0000000f 0 00000011 winedevice.exe 00000017 0 00000016 0 00000013 0 00000012 0 00000018 explorer.exe 00000019 0 00000023 rpcss.exe 00000033 0 00000032 0 0000002e 0 0000002c rpcss.exe 00000034 0 0000002f 0 00000030 0 00000022 (D) Z:\home\dank\wine-git\dlls\ntdll\tests\ntdll_test.exe 0000003e 0 <== 0000003a ole32_test.exe 00000046 0 Backtrace: =>0 0x7f230000 (0x7f22fcb8) 1 0x0495af5b test_prot_fault+0x6b() [/home/dank/wine-git/dlls/ntdll/tests/exception.c:418] in ntdll_test (0x7f22fcf8) 2 0x0495d568 func_exception+0x38e() [/home/dank/wine-git/dlls/ntdll/tests/exception.c:1433] in ntdll_test (0x7f22fd28) 3 0x0498ced4 run_test+0x9f(name="exception.c") [/home/dank/wine-git/dlls/ntdll/tests/../../../include/wine/test.h:543] in ntdll_test (0x7f22fd88) 4 0x0498d1ee main+0x1f1(argc=0x7f22fe70, argv=0x7f001cf8) [/home/dank/wine-git/dlls/ntdll/tests/../../../include/wine/test.h:592] in ntdll_test (0x7f22fe58) 5 0x0498d27e __wine_spec_exe_entry+0x6a(peb=0x7ffdf000) [/home/dank/wine-git/dlls/winecrt0/exe_entry.c:36] in ntdll_test (0x7f22fe98) 6 0x04854ba4 start_process+0x137(peb=0x7ffdf000) [/home/dank/wine-git/dlls/kernel32/process.c:1028] in kernel32 (0x7f22fed8) 7 0x047569f0 call_thread_func+0xc() in ntdll (0x7f22fee8) 8 0x04756a2e call_thread_entry_point+0x34(entry=0x4854a6d, arg=0x7ffdf000) [/home/dank/wine-git/dlls/ntdll/signal_i386.c:2457] in ntdll (0x7f22ffc8) 9 0x0472f736 LdrInitializeThunk(kernel_start=0x7ffdf000, unknown2=0, unknown3=0, unknown4=0) [/home/dank/wine-git/dlls/ntdll/loader.c:2621] in ntdll (0x7f22ffe8) valgrind: Unrecognised instruction at address 0x7f230000. Your program just tried to execute an instruction that Valgrind did not recognise. There are two possible reasons for this. 1. Your program has a bug and erroneously jumped to a non-code location. If you are running Memcheck and you just saw a warning about a bad jump, it's probably your program's fault. 2. The instruction is legitimate but Valgrind doesn't handle it, i.e. it's Valgrind's fault. If you think this is the case or you are not sure, please let us know and we'll try to fix it. Either way, Valgrind will now raise a SIGILL signal which will probably kill your program. err:seh:segv_handler Got unexpected trap 0 exception.c:371: Test failed: 15: Wrong exception code c000001d/c0000005 exception.c:373: Test failed: 15: Wrong exception address 0x7f230000/0x7f230006 exception.c:377: Test failed: 15: Wrong number of parameters 0/2 exception.c:371: Test failed: 15: Wrong exception code c000001d/c0000005 exception.c:373: Test failed: 15: Wrong exception address 0x7f230000/0x7f230006 exception.c:377: Test failed: 15: Wrong number of parameters 0/2 Conditional jump or move depends on uninitialised value(s) at handler (exception.c:384) by ??? (signal_i386.c:2478) by ??? (signal_i386.c:2478) by __regs_RtlUnwind (signal_i386.c:2351) by __wine_call_from_regs (in /home/dank/wine-git/dlls/ntdll/ntdll.dll.so) by ??? (signal_i386.c:2367) by __wine_unwind_frame (exception.h:294) by __wine_exception_handler (exception.h:319) by ??? (signal_i386.c:2478) by ??? (signal_i386.c:2478) by call_stack_handlers (signal_i386.c:606) by raise_exception (signal_i386.c:684) by NtRaiseException (signal_i386.c:2376) by raise_segv_exception (signal_i386.c:1709) by ??? by test_prot_fault (exception.c:416) by func_exception (exception.c:1432) by run_test (test.h:541) by main (test.h:591) Uninitialised value was created by a client request at setup_exception_record (signal_i386.c:1587) by segv_handler (signal_i386.c:1834) by ??? (in /lib/tls/i686/cmov/libpthread-2.10.1.so) { Memcheck:Cond fun:handler obj:/home/dank/wine-git/dlls/ntdll/ntdll.dll.so obj:/home/dank/wine-git/dlls/ntdll/ntdll.dll.so fun:__regs_RtlUnwind fun:__wine_call_from_regs obj:/home/dank/wine-git/dlls/ntdll/ntdll.dll.so fun:__wine_unwind_frame fun:__wine_exception_handler obj:/home/dank/wine-git/dlls/ntdll/ntdll.dll.so obj:/home/dank/wine-git/dlls/ntdll/ntdll.dll.so fun:call_stack_handlers fun:raise_exception fun:NtRaiseException fun:raise_segv_exception obj:* fun:test_prot_fault fun:func_exception fun:run_test fun:main } HEAP SUMMARY: in use at exit: 261,170 bytes in 4,520 blocks total heap usage: 21,036 allocs, 16,516 frees, 5,413,805 bytes allocated HEAP SUMMARY: in use at exit: 38,419 bytes in 165 blocks total heap usage: 3,569 allocs, 3,404 frees, 24,761,352 bytes allocated LEAK SUMMARY: definitely lost: 0 bytes in 0 blocks indirectly lost: 120 bytes in 10 blocks possibly lost: 0 bytes in 0 blocks still reachable: 187,086 bytes in 1,815 blocks suppressed: 73,964 bytes in 2,695 blocks Reachable blocks (those to which a pointer was found) are not shown. To see them, rerun with: --leak-check=full --show-reachable=yes For counts of detected and suppressed errors, rerun with: -v ERROR SUMMARY: 4 errors from 2 contexts (suppressed: 293 from 94) used_suppression: 94 todo_suppress_libfontconfig_leak used_suppression: 143 todo_suppress_dlopen_leak used_suppression: 1 suppress_nss_leak used_suppression: 2 todo_wine_dlls_winex11drv__X11DRV_XRender_Init used_suppression: 2 todo_wine_dlls_winex11drv__X11DRV_XComposite_Init used_suppression: 2 todo_wine_dlls_winex11drv__X11DRV_XRandR_Init used_suppression: 2 todo_wine_dlls_winex11drv__X11DRV_XF86VM_Init used_suppression: 4 todo_wine_dlls_winex11drv__xinerama_init used_suppression: 2 todo_wine_dlls_winex11drv__XkbUseExtension used_suppression: 1 user32_builtin_classes_leak used_suppression: 1 todo_suppress_wine_init_load_order_leak used_suppression: 1 todo_suppress_wine_alloc_module_leak used_suppression: 1 todo_wine_dlls_winex11drv_XOpenDisplay used_suppression: 56 glibc-2.10-on-SUSE-10.3-(x86) used_suppression: 199 dl-hack3-cond-1