--- Comment #6 from ---
Created attachment 107183
Instrumented guest_amd64_toIR.c

I have instrumented guest_amd64_toIR.c and line number 20564 seems to be the
source of my issue:

==17761== Memcheck, a memory error detector
==17761== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==17761== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==17761== Command: /bin/bash
DEBUG Line no 20564
DEBUG Line no 32358
vex amd64->IR: unhandled instruction bytes: 0x8F 0xEA 0x78 0x10 0xD0 0x8 0x4
0x0 0x0 0x89
vex amd64->IR:   REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR:   VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR:   PFX.66=0 PFX.F2=0 PFX.F3=0
==17761== valgrind: Unrecognised instruction at address 0x401b8b9.
==17761==    at 0x401B8B9: get_common_indeces.constprop.1 (in /lib/
==17761==    by 0x401C0B3: _dl_sysdep_start (in /lib/
==17761==    by 0x4001F17: _dl_start (in /lib/
==17761==    by 0x4000F47: ??? (in /lib/
==17761== Your program just tried to execute an instruction that Valgrind
==17761== did not recognise.  There are two possible reasons for this.
==17761== 1. Your program has a bug and erroneously jumped to a non-code
==17761==    location.  If you are running Memcheck and you just saw a
==17761==    warning about a bad jump, it's probably your program's fault.
==17761== 2. The instruction is legitimate but Valgrind doesn't handle it,
==17761==    i.e. it's Valgrind's fault.  If you think this is the case or
==17761==    you are not sure, please let us know and we'll try to fix it.
==17761== Either way, Valgrind will now raise a SIGILL signal which will
==17761== probably kill your program.
==17761== Process terminating with default action of signal 4 (SIGILL)
==17761==  Illegal opcode at address 0x401B8B9
==17761==    at 0x401B8B9: get_common_indeces.constprop.1 (in /lib/
==17761==    by 0x401C0B3: _dl_sysdep_start (in /lib/
==17761==    by 0x4001F17: _dl_start (in /lib/
==17761==    by 0x4000F47: ??? (in /lib/
==17761== HEAP SUMMARY:
==17761==     in use at exit: 0 bytes in 0 blocks
==17761==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==17761== All heap blocks were freed -- no leaks are possible
==17761== For counts of detected and suppressed errors, rerun with: -v
==17761== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Illegal instruction

You are receiving this mail because:
You are watching all bug changes.

Reply via email to