Hi Joel, I'm just starting to plow through the problems. I think base_unittests is about ok now, but net_unittests explodes wherever it tries to use v8, with the same error you had.
I guess v8 isn't happy with valgrind on 64 bits yet; I'll report this upstream. - Dan On 16 Sep., 21:20, Joel Stanley <[email protected]> wrote: > Hello, > > While attempting to run x64 unit_tests under valgrind I am hitting an error: > > vex: priv/guest_amd64_toIR.c:14600 (disInstr_AMD64_WRK): Assertion `sz > == 2 || sz == 4' failed. > vex storage: T total 4600074960 bytes allocated > vex storage: P total 816 bytes allocated > > valgrind: the 'impossible' happened: > LibVEX called failure_exit(). > ==25306== at 0x3802ADC4: report_and_quit (m_libcassert.c:145) > ==25306== by 0x3802AE29: panic (m_libcassert.c:227) > ==25306== by 0x3802AEA2: vgPlain_core_panic_at (m_libcassert.c:232) > ==25306== by 0x3802AEC1: vgPlain_core_panic (m_libcassert.c:237) > ==25306== by 0x380433F2: failure_exit (m_translate.c:674) > ==25306== by 0x380B2AE8: vex_assert_fail (main_util.c:220) > ==25306== by 0x38117CCE: disInstr_AMD64_WRK (guest_amd64_toIR.c:14600) > ==25306== by 0x3811BB42: disInstr_AMD64 (guest_amd64_toIR.c:16116) > ==25306== by 0x380C0BA1: bb_to_IR (guest_generic_bb_to_IR.c:229) > ==25306== by 0x380B135C: LibVEX_Translate (main_main.c:420) > ==25306== by 0x380410B5: vgPlain_translate (m_translate.c:1517) > ==25306== by 0x38062F68: vgPlain_scheduler (scheduler.c:844) > ==25306== by 0x3808AF74: run_a_thread_NORETURN (syswrap-linux.c:91) > > Has anyone had success valgrinding 64bit binaries? > > Cheers, > > Joel --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
