https://bugs.kde.org/show_bug.cgi?id=211031
--- Comment #16 from Austin English <austinengl...@gmail.com> --- I recently tested llvm-mingw (from https://github.com/mstorsjo/llvm-mingw/), and built wine with llvm's pdb debug symbols. That gives similar results to gnu mingw: ==23786== Invalid read of size 2 ==23786== at 0x7B01F09E: ??? ==23786== by 0x60B93DA: ??? ==23786== by 0x60B89AC: ??? ==23786== by 0x507872F: ??? (in /home/austin/wine-valgrind-mingw/dlls/user32/user32.dll.so) ==23786== by 0x5078CFE: call_window_proc (winproc.c:249) ==23786== by 0x507A02C: WINPROC_CallProcAtoW (winproc.c:609) ==23786== by 0x507ABC4: WINPROC_call_window (winproc.c:956) ==23786== by 0x5043C8D: call_window_proc (message.c:2225) ==23786== by 0x5046E09: send_message (message.c:3294) ==23786== by 0x50498B9: SendMessageA (message.c:3517) ==23786== by 0x41C0A6: ??? ==23786== by 0x4143D1: ??? ==23786== by 0x49F862: ??? ==23786== by 0x49F71C: ??? ==23786== by 0x401394: ??? ==23786== by 0x7B449E31: ??? (in /home/austin/wine-valgrind-mingw/dlls/kernel32/kernel32.dll.so) ==23786== by 0x7B44A262: start_process (process.c:153) ==23786== by 0x7B449E3D: ??? (in /home/austin/wine-valgrind-mingw/dlls/kernel32/kernel32.dll.so) ==23786== Address 0x5ec1a08 is 744 bytes inside a block of size 1,024 free'd ==23786== at 0x7BC6255E: notify_free (heap.c:268) ==23786== by 0x7BC64B94: RtlFreeHeap (heap.c:1771) ==23786== by 0x52123C3: free_heap_bits (bitblt.c:168) ==23786== by 0x521CF08: nulldrv_StretchDIBits (dib.c:606) ==23786== by 0x521D285: StretchDIBits (dib.c:636) ==23786== by 0x500C450: create_icon_from_bmi (cursoricon.c:1265) ==23786== by 0x500D26B: CURSORICON_Load (cursoricon.c:1867) ==23786== by 0x500F153: LoadImageW (cursoricon.c:3065) ==23786== by 0x6111289: ??? ==23786== by 0x60B1CE7: ??? ==23786== by 0x61221E0: ??? ==23786== by 0x7BC667C9: ??? (in /home/austin/wine-valgrind-mingw/dlls/ntdll/ntdll.dll.so) ==23786== by 0x7BC6A582: MODULE_InitDLL (loader.c:1331) ==23786== by 0x7BC6A80A: process_attach (loader.c:1425) ==23786== by 0x7BC6CBD2: LdrLoadDll (loader.c:3094) ==23786== by 0x7B01436E: ??? ==23786== by 0x7B014279: ??? ==23786== by 0x7B01419B: ??? ==23786== by 0x7B01415E: ??? ==23786== by 0x4145B5: ??? ==23786== Block was alloc'd at ==23786== at 0x7BC62514: notify_alloc (heap.c:260) ==23786== by 0x7BC65377: RtlAllocateHeap (heap.c:1725) ==23786== by 0x5212AB4: convert_bits (bitblt.c:183) ==23786== by 0x521D045: nulldrv_StretchDIBits (dib.c:589) ==23786== by 0x521D285: StretchDIBits (dib.c:636) ==23786== by 0x500C450: create_icon_from_bmi (cursoricon.c:1265) ==23786== by 0x500D26B: CURSORICON_Load (cursoricon.c:1867) ==23786== by 0x500F153: LoadImageW (cursoricon.c:3065) ==23786== by 0x6111289: ??? ==23786== by 0x60B1CE7: ??? ==23786== by 0x61221E0: ??? ==23786== by 0x7BC667C9: ??? (in /home/austin/wine-valgrind-mingw/dlls/ntdll/ntdll.dll.so) ==23786== by 0x7BC6A582: MODULE_InitDLL (loader.c:1331) ==23786== by 0x7BC6A80A: process_attach (loader.c:1425) ==23786== by 0x7BC6CBD2: LdrLoadDll (loader.c:3094) ==23786== by 0x7B01436E: ??? ==23786== by 0x7B014279: ??? ==23786== by 0x7B01419B: ??? ==23786== by 0x7B01415E: ??? ==23786== by 0x4145B5: ??? ==23786== which is interesting, given that valgrind has some pdb support. LLVM uses the publicly documented pdb info from https://github.com/Microsoft/microsoft-pdb, fwiw. Note that I did run until other issues in some tests with this setup, see bug 416779. Tested with VALGRIND_3_15_0-193-gfe6805efc -- You are receiving this mail because: You are watching all bug changes.
