On Fri, Mar 27, 2009 at 4:01 AM, Julian Seward <[email protected]> wrote: > On Friday 27 March 2009, Johan Björk wrote: >> Look at revision r9466 in the DARWIN branch. Issue is that VEX got >> updated but not the mainbranch. > > Try rebuilding from clean. The build system is kinda borked > w.r.t. dependencies and I think this is a case where you got > bitten. I did hack around with the vex interface on darwin, > but I then fixed up {x86,amd64,ppc32,ppc64}-linux on the > trunk to match, so I think a clean rebuild should sort it out.
No joy. Even a completely clean recheckout and build fails with MC_(get_otrack_shadow_offset)(x86)(off=320,sz=4) Memcheck: mc_machine.c:672 (get_otrack_shadow_offset_wrk): the 'impossible' happened. ==9537== at 0x380244CD: report_and_quit (m_libcassert.c:140) ==9537== by 0x380247D1: vgPlain_assert_fail (m_libcassert.c:205) ==9537== by 0x3801DDDD: vgMemCheck_get_otrack_shadow_offset (mc_machine.c:672) ==9537== by 0x3801864A: schemeS (mc_translate.c:4295) ==9537== by 0x3801D345: vgMemCheck_instrument (mc_translate.c:3578) ==9537== by 0x380B6C7B: LibVEX_Translate (vex_main.c:500) ==9537== by 0x3803B541: vgPlain_translate (m_translate.c:1506) ==9537== by 0x3804BC1F: vgPlain_scheduler (scheduler.c:796) ==9537== by 0x38065C08: run_a_thread_NORETURN (syswrap-linux.c:89) so bug https://bugs.kde.org/show_bug.cgi?id=188161 is most definitely still a problem. - Dan ------------------------------------------------------------------------------ _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
