Disassembly failure at ExecMsg 1!

[WenjieZheng1998]

ngiezheng@angiezheng-virtual-machine:/下载/valgrind-3.12.0$ valgrind --tool=tracergrind --output=hello.trace helloworld/hello
==21191== TracerGrind-1.4, TracerGrind tracing tool
==21191== Charles Hubain
==21191== Using Valgrind-3.12.0 and LibVEX; rerun with -h for copyright info
==21191== Command: helloworld/hello
==21191==
vex amd64->IR: unhandled instruction bytes: 0xF3 0xF 0x1E 0xFA 0x55 0x48 0x89 0xE5 0x41 0x57
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=0F
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=1
==21191== valgrind: Unrecognised instruction at address 0x4001df0.
==21191== at 0x4001DF0: ??? (in /usr/lib/x86_64-linux-gnu/ld-2.31.so)
==21191== by 0x4001107: ??? (in /usr/lib/x86_64-linux-gnu/ld-2.31.so)
==21191== Your program just tried to execute an instruction that Valgrind
==21191== did not recognise. There are two possible reasons for this.
==21191== 1. Your program has a bug and erroneously jumped to a non-code
==21191== location. If you are running Memcheck and you just saw a
==21191== warning about a bad jump, it's probably your program's fault.
==21191== 2. The instruction is legitimate but Valgrind doesn't handle it,
==21191== i.e. it's Valgrind's fault. If you think this is the case or
==21191== you are not sure, please let us know and we'll try to fix it.
==21191== Either way, Valgrind will now raise a SIGILL signal which will
==21191== probably kill your program.
==21191==
==21191== Process terminating with default action of signal 4 (SIGILL)
==21191== Illegal opcode at address 0x4001DF0
==21191== at 0x4001DF0: ??? (in /usr/lib/x86_64-linux-gnu/ld-2.31.so)
==21191== by 0x4001107: ??? (in /usr/lib/x86_64-linux-gnu/ld-2.31.so)
==21191==
非法指令 (核心已转储)
angiezheng@angiezheng-virtual-machine:/下载/valgrind-3.12.0$ texttrace hello.trace hello.texttrace
Disassembly failure at ExecMsg 1!
I meet a wrong like this, but I don't know the where is the missing.