https://bugs.kde.org/show_bug.cgi?id=471036
--- Comment #4 from Matthias Schwarzott <z...@gentoo.org> --- I tested the attachment "Example patch for guest_amd64_toIR" https://bugs.kde.org/attachment.cgi?id=159662 It perfectly fixes the problem. Without fix (but extended context-printing) the extended bmi testcase fails like this: shrx32 0000000000000000 0000000000000000 -> 0000000000000000 current %rip = 0x109ABE assumed next %rip = 0x109AC7 actual next %rip = 0x109AC8 instruction bytes: 0xC4 0xE3 0xFB 0xF0 0xD 0x60 0x45 0x0 0x0 0x43 vex: the `impossible' happened: disInstr_AMD64: disInstr miscalculated next %rip vex storage: T total 171126616 bytes allocated vex storage: P total 512 bytes allocated valgrind: the 'impossible' happened: LibVEX called failure_exit(). host stacktrace: ==20396== at 0x5804383A: show_sched_status_wrk (m_libcassert.c:407) ==20396== by 0x58043957: report_and_quit (m_libcassert.c:478) ==20396== by 0x58043BAB: panic (m_libcassert.c:554) ==20396== by 0x58043BAB: vgPlain_core_panic_at (m_libcassert.c:559) ==20396== by 0x58043BCA: vgPlain_core_panic (m_libcassert.c:564) ==20396== by 0x58058034: failure_exit (m_translate.c:761) ==20396== by 0x5813068A: vpanic (main_util.c:253) ==20396== by 0x581BBDDD: disInstr_AMD64 (guest_amd64_toIR.c:32714) ==20396== by 0x58148E76: disassemble_basic_block_till_stop.constprop.0 (guest_generic_bb_to_IR.c:956) ==20396== by 0x5814965C: bb_to_IR (guest_generic_bb_to_IR.c:1365) ==20396== by 0x5812D6AF: LibVEX_FrontEnd (main_main.c:583) ==20396== by 0x5812E00C: LibVEX_Translate (main_main.c:1235) ==20396== by 0x5805A791: vgPlain_translate (m_translate.c:1831) ==20396== by 0x58097F3B: handle_chain_me (scheduler.c:1164) ==20396== by 0x5809A42B: vgPlain_scheduler (scheduler.c:1531) ==20396== by 0x580E5569: thread_wrapper (syswrap-linux.c:102) ==20396== by 0x580E5569: run_a_thread_NORETURN (syswrap-linux.c:155) sched status: running_tid=1 Thread 1: status = VgTs_Runnable (lwpid 20396) ==20396== at 0x1099FC: do_rorx64 (bmi.c:379) ==20396== by 0x10AEDC: main (bmi.c:1012) client stack range: [0x1FFEFFD000 0x1FFF000FFF] client SP: 0x1FFEFFF258 valgrind stack range: [0x1002DEB000 0x1002EEAFFF] top usage: 10960 of 1048576 -- You are receiving this mail because: You are watching all bug changes.
