http://bugs.winehq.org/show_bug.cgi?id=11211
--- Comment #1 from Dan Kegel dank@kegel.com 2008-01-16 20:08:54 --- Uh-oh. I'm seeing this on random invocations of winedbg now:
==17621== by 0x4709BCB: raise_segv_exception (signal_i386.c:1162) ==17621== by 0xDEADBABD: ??? ==17621== by 0x4961274: pool_strdup (storage.c:111) ==17621== by 0x496246C: symt_new_function (symbol.c:233) ==17621== by 0x4949761: dwarf2_parse_subprogram (dwarf.c:1564) ==17621== by 0x4949AE6: dwarf2_load_one_entry (dwarf.c:1721) ==17621== by 0x494A765: dwarf2_parse_compilation_unit (dwarf.c:2014) ==17621== by 0x494AE81: dwarf2_parse (dwarf.c:2217) ==17621== by 0x494CF0B: elf_load_debug_info_from_map (elf_module.c:241) ==17621== by 0x494D3E6: elf_load_debug_info (elf_module.c:1143) ==17621== by 0x4950FCA: module_get_debug (module.c:303) ==17621== by 0x4964617: SymFromAddr (symbol.c:1043) ==17621== by 0x48F9E61: stack_print_addr_and_args (stack.c:250) ==17621== by 0x48FA0B2: backtrace (stack.c:293)
This is valgrind showing a backtrace from our own backtrace crashing?!
Invoked like this: cd dlls/comctl32 WINEDEBUG=+seh,+process ../../../tools/runtest -P wine -M comctl32.dll -T ../../.. -p comctl32_test.exe.so imagelist.c I'll attach the full log.