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 0040), 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:049acff4 ECX:04995eb5 EDX:7f22fc98 ESI:7f22fe70 EDI:00000000 Stack dump: 0x7f22fc7c: 0495b50a 7f230000 04995eb4 00000012 0x7f22fc8c: 0498de6e 00000001 049965cf 7f22ff08 0x7f22fc9c: 0495bbeb 04995eb4 00000040 7f22fcc8 0x7f22fcac: 7f230000 7f002258 049acff4 7f22fcf8 0x7f22fcbc: 0495bf5b 0495bbeb 04995eb4 04995eb4 0x7f22fccc: 00000012 00000000 7f22fce0 00000000 Backtrace: =>0 0x7f230000 (0x7f22fcb8) 1 0x0495bf5b test_prot_fault+0x6b() [/home/dank/wine-git/dlls/ntdll/tests/exception.c:418] in ntdll_test (0x7f22fcf8) 2 0x0495e568 func_exception+0x38e() [/home/dank/wine-git/dlls/ntdll/tests/exception.c:1433] in ntdll_test (0x7f22fd28) 3 0x0498e670 run_test+0x9f(name="exception.c") [/home/dank/wine-git/dlls/ntdll/tests/../../../include/wine/test.h:543] in ntdll_test (0x7f22fd88) 4 0x0498e98a main+0x1f1(argc=0x7f22fe70, argv=0x7f001cc0) [/home/dank/wine-git/dlls/ntdll/tests/../../../include/wine/test.h:592] in ntdll_test (0x7f22fe58) 5 0x0498ea1a __wine_spec_exe_entry+0x6a(peb=0x7ffdf000) [/home/dank/wine-git/dlls/winecrt0/exe_entry.c:36] in ntdll_test (0x7f22fe98) 6 0x048554b8 start_process+0x137(peb=0x7ffdf000) [/home/dank/wine-git/dlls/kernel32/process.c:992] in kernel32 (0x7f22fed8) 7 0x04757a98 call_thread_func+0xc() in ntdll (0x7f22fee8) 8 0x04757ad6 call_thread_entry_point+0x34(entry=0x4855381, arg=0x7ffdf000) [/home/dank/wine-git/dlls/ntdll/signal_i386.c:2457] in ntdll (0x7f22ffc8) 9 0x04730736 LdrInitializeThunk(kernel_start=0x7ffdf000, unknown2=0, unknown3=0, unknown4=0) [/home/dank/wine-git/dlls/ntdll/loader.c:2621] in ntdll (0x7f22ffe8) 10 0x04032ed5 wine_call_on_stack+0x1d() in libwine.so.1 (0x00000000) 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 Dwarf libwine.so.1 ELF 4179000- 4192000 Deferred libpthread.so.0 ELF 4193000- 42d8000 Deferred libc.so.6 ELF 42d8000- 42dc000 Deferred libdl.so.2 ELF 46dd000- 479e000 Dwarf ntdll \-PE 46f0000- 479e000 \ ntdll ELF 479e000- 47c4000 Deferred libm.so.6 ELF 47c4000- 47cc000 Deferred libnss_compat.so.2 ELF 47cc000- 47e3000 Deferred libnsl.so.1 ELF 47e3000- 47ee000 Deferred libnss_nis.so.2 ELF 47ee000- 47fa000 Deferred libnss_files.so.2 ELF 47fa000- 4939000 Dwarf kernel32 \-PE 4810000- 4939000 \ kernel32 ELF 4939000- 49af000 Dwarf ntdll_test \-PE 4940000- 49af000 \ ntdll_test ELF 49af000- 4ad1000 Deferred user32 \-PE 49c0000- 4ad1000 \ user32 ELF 4ad1000- 4b6b000 Deferred gdi32 \-PE 4ae0000- 4b6b000 \ gdi32 ELF 4b6b000- 4bc7000 Deferred advapi32 \-PE 4b80000- 4bc7000 \ advapi32 ELF 4bc7000- 4c40000 Deferred rpcrt4 \-PE 4bd0000- 4c40000 \ rpcrt4 ELF 4c40000- 4cbf000 Deferred libfreetype.so.6 ELF 4cbf000- 4cd5000 Deferred libz.so.1 ELF 4cd5000- 4d02000 Deferred libfontconfig.so.1 ELF 4d02000- 4d29000 Deferred libexpat.so.1 ELF 4d81000- 4d8a000 Deferred libsm.so.6 ELF 4d8a000- 4d9a000 Deferred libxext.so.6 ELF 4d9a000- 4d9f000 Deferred libuuid.so.1 ELF 51a0000- 5252000 Deferred winex11 \-PE 51b0000- 5252000 \ winex11 ELF 5252000- 526d000 Deferred libice.so.6 ELF 526d000- 539c000 Deferred libx11.so.6 ELF 539c000- 53a0000 Deferred libxau.so.6 ELF 53a0000- 53be000 Deferred libxcb.so.1 ELF 53be000- 53c3000 Deferred libxdmcp.so.6 ELF 53c3000- 53e4000 Deferred imm32 \-PE 53d0000- 53e4000 \ imm32 ELF 53e4000- 53e7000 Deferred libxinerama.so.1 ELF 53e7000- 53ed000 Deferred libxxf86vm.so.1 ELF 53ed000- 53f7000 Deferred libxrender.so.1 ELF 53f7000- 5400000 Deferred libxrandr.so.2 ELF 5400000- 5404000 Deferred libxcomposite.so.1 ELF 5404000- 540a000 Deferred libxfixes.so.3 ELF 540a000- 5415000 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 00000018 0 00000017 0 00000013 0 00000012 0 00000019 explorer.exe 0000001a 0 0000002e rpcss.exe 00000031 0 00000036 0 00000037 0 00000033 rpcss.exe 0000003d 0 0000003f 0 00000034 0 00000022 (D) Z:\home\dank\wine-git\dlls\ntdll\tests\ntdll_test.exe 00000040 0 <== Backtrace: =>0 0x7f230000 (0x7f22fcb8) 1 0x0495bf5b test_prot_fault+0x6b() [/home/dank/wine-git/dlls/ntdll/tests/exception.c:418] in ntdll_test (0x7f22fcf8) 2 0x0495e568 func_exception+0x38e() [/home/dank/wine-git/dlls/ntdll/tests/exception.c:1433] in ntdll_test (0x7f22fd28) 3 0x0498e670 run_test+0x9f(name="exception.c") [/home/dank/wine-git/dlls/ntdll/tests/../../../include/wine/test.h:543] in ntdll_test (0x7f22fd88) 4 0x0498e98a main+0x1f1(argc=0x7f22fe70, argv=0x7f001cc0) [/home/dank/wine-git/dlls/ntdll/tests/../../../include/wine/test.h:592] in ntdll_test (0x7f22fe58) 5 0x0498ea1a __wine_spec_exe_entry+0x6a(peb=0x7ffdf000) [/home/dank/wine-git/dlls/winecrt0/exe_entry.c:36] in ntdll_test (0x7f22fe98) 6 0x048554b8 start_process+0x137(peb=0x7ffdf000) [/home/dank/wine-git/dlls/kernel32/process.c:992] in kernel32 (0x7f22fed8) 7 0x04757a98 call_thread_func+0xc() in ntdll (0x7f22fee8) 8 0x04757ad6 call_thread_entry_point+0x34(entry=0x4855381, arg=0x7ffdf000) [/home/dank/wine-git/dlls/ntdll/signal_i386.c:2457] in ntdll (0x7f22ffc8) 9 0x04730736 LdrInitializeThunk(kernel_start=0x7ffdf000, unknown2=0, unknown3=0, unknown4=0) [/home/dank/wine-git/dlls/ntdll/loader.c:2621] in ntdll (0x7f22ffe8) 10 0x04032ed5 wine_call_on_stack+0x1d() in libwine.so.1 (0x00000000) 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: 270,291 bytes in 4,773 blocks total heap usage: 25,351 allocs, 20,578 frees, 6,099,636 bytes allocated LEAK SUMMARY: definitely lost: 0 bytes in 0 blocks indirectly lost: 120 bytes in 10 blocks possibly lost: 2,276 bytes in 3 blocks still reachable: 188,599 bytes in 1,966 blocks suppressed: 79,296 bytes in 2,794 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: 7 errors from 5 contexts (suppressed: 294 from 95) 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 HEAP SUMMARY: in use at exit: 44,886 bytes in 128 blocks total heap usage: 4,004 allocs, 3,876 frees, 30,716,046 bytes allocated