[Valgrind-users] unhandled instruction bytes for vmovdqu64

[Simon S. <sim...@gn...>]

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)

Using vgdb there were the following details:

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
138
139 744             string_ptr = NULL;
140    0x0000000004e75f26 <+6>:     movq   $0x0,0x244e6f(%rip)        # 
0x50bada0 <string_ptr>
141
142 742             string_dst_copy = *dst;
143    0x0000000004e75f31 <+17>:    vmovaps %xmm0,0x244e47(%rip) # 
0x50bad80 <string_dst_copy>
144    0x0000000004e75f39 <+25>:    mov    0x10(%rdi),%rax
145    0x0000000004e75f3d <+29>:    mov    %rax,0x244e4c(%rip)        # 
0x50bad90 <string_dst_copy+16>
146
147 743             string_dst = &string_dst_copy;
148    0x0000000004e75f44 <+36>:    lea    0x244e35(%rip),%rax        # 
0x50bad80 <string_dst_copy>
149    0x0000000004e75f4b <+43>:    mov    %rax,0x244e56(%rip)        # 
0x50bada8 <string_dst>


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

Thanks,
Simon