|
From: Dan K. <da...@ke...> - 2008-06-16 21:42:42
|
This happened with source a couple weeks old, and persists with up to date source from svn. --16448-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting --16448-- si_code=2; Faulting address: 0xBEEF0008; sp: 0x6838ECFC valgrind: the 'impossible' happened: Killed by fatal signal ==16448== at 0x38037B72: vgPlain_get_StackTrace_wrk (m_stacktrace.c:166) ==16448== by 0x38037D12: vgPlain_get_StackTrace (m_stacktrace.c:480) ==16448== by 0x380251D3: record_ExeContext_wrk (m_execontext.c:316) ==16448== by 0x38001651: die_and_free_mem (mc_malloc_wrappers.c:300) ==16448== by 0x380019E5: vgMemCheck_free (mc_malloc_wrappers.c:328) ==16448== by 0x38048552: do_client_request (scheduler.c:1303) ==16448== by 0x38049323: vgPlain_scheduler (scheduler.c:1013) ==16448== by 0x3804C2C4: run_a_thread_NORETURN (syswrap-linux.c:89) To try to reproduce, grab latest wine source, apply http://kegel.com/wine/valgrind/runtest.patch and do cd dlls/ddraw/tests RUNTEST_USE_VALGRIND=1 ../../../tools/runtest -P wine -M ddraw.dll -T ../../.. -p ddraw_test.exe.so dsurface.c however this doesn't happen on at least one of my machines, so it might be tricky to reproduce. I stand ready to give more info, file a bug report, or whatever. Thanks! - Dan |