On 3/7/06, Dan Kegel dank@kegel.com wrote:
I'm trying to track down a wine crash in firefox (http://bugs.winehq.org/show_bug.cgi?id=4762) and thought valgrind might be helpful. So, following http://wiki.winehq.org/Wine_and_Valgrind
When I posted the above, I hadn't yet applied the patch mentioned in the wiki page. When I did, valgrind itself crapped out:
==18736== Warning: client switching stacks? SP change: 0xBE857B4C --> 0x48DFFF0 ==18736== to suppress, use: --max-stackframe=1174963364 or greater --18707-- INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting --18707-- si_code=1; Faulting address: 0x57E58959; sp: 0x62527DA4
valgrind: the 'impossible' happened: Killed by fatal signal ==18707== at 0xB001AB5C: vgPlain_get_StackTrace2 (m_stacktrace.c:147) ==18707== by 0xB001AC31: vgPlain_get_StackTrace (m_stacktrace.c:331) ==18707== by 0xB000DDCF: vgPlain_record_ExeContext (m_execontext.c:199) ==18707== by 0xB0001116: create_MAC_Chunk (mac_malloc_wrappers.c:139) ==18707== by 0xB0001B17: vgMAC_malloc (mac_malloc_wrappers.c:203) ==18707== by 0xB002D9C3: do_client_request (scheduler.c:987) ==18707== by 0xB002D498: vgPlain_scheduler (scheduler.c:721) ==18707== by 0xB003BB99: thread_wrapper (syswrap-linux.c:86) ==18707== by 0xB003BC5D: run_a_thread_NORETURN (syswrap-linux.c:119)
so I guess there's definitely some work left to do on valgrind... - Dan
-- Wine for Windows ISVs: http://kegel.com/wine/isv