Re: [Valgrind-users] unhandled instruction bytes for vmovdqu64

[John R. <jr...@bi...>]

> Running valgrind on GnuCOBOL errors out with
> 
> vex amd64->IR: unhandled instruction bytes:
>       0x62 0xF1 0xFE 0x8 0x6F 0x7 0x48 0xC7 0x5 0x6F
> 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
> valgrind: Unrecognised instruction at address 0x4e75f20.
>    at 0x4E75F20: cob_string_init (strings.c:742)

> 132 (gdb) disassemble /s
> 133 Dump of assembler code for function cob_string_init:
> 134 ../../libcob/strings.c:
> 135 741     {
> 136 742             string_dst_copy = *dst;
> 137 => 0x0000000004e75f20 <+0>:     vmovdqu64 (%rdi),%xmm0

> Is there anything I can do this to still run the application with valgrind or do I need to wait for a hotfix?

As always: report the version of valgrind.  Run "valgrind --version",
then copy+paste the output here.  The version is the #1 clue for any investigation.