[C]$ valgrind --leak-check=yes ./chars
==17507== Memcheck, a memory error detector
==17507== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==17507== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==17507== Command: ./chars
==17507==
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
==17507== valgrind: Unrecognised instruction at address 0x4016bd9.
==17507==    at 0x4016BD9: get_common_indeces.constprop.1 (in /lib64/ld-2.25.so)
==17507==    by 0x4017140: _dl_sysdep_start (in /lib64/ld-2.25.so)
==17507==    by 0x40019F1: _dl_start (in /lib64/ld-2.25.so)
==17507==    by 0x4000B87: ??? (in /lib64/ld-2.25.so)
==17507== Your program just tried to execute an instruction that Valgrind
==17507== did not recognise.  There are two possible reasons for this.
==17507== 1. Your program has a bug and erroneously jumped to a non-code
==17507==    location.  If you are running Memcheck and you just saw a
==17507==    warning about a bad jump, it's probably your program's fault.
==17507== 2. The instruction is legitimate but Valgrind doesn't handle it,
==17507==    i.e. it's Valgrind's fault.  If you think this is the case or
==17507==    you are not sure, please let us know and we'll try to fix it.
==17507== Either way, Valgrind will now raise a SIGILL signal which will
==17507== probably kill your program.
==17507==
==17507== Process terminating with default action of signal 4 (SIGILL)
==17507==  Illegal opcode at address 0x4016BD9
==17507==    at 0x4016BD9: get_common_indeces.constprop.1 (in /lib64/ld-2.25.so)
==17507==    by 0x4017140: _dl_sysdep_start (in /lib64/ld-2.25.so)
==17507==    by 0x40019F1: _dl_start (in /lib64/ld-2.25.so)
==17507==    by 0x4000B87: ??? (in /lib64/ld-2.25.so)
==17507==
==17507== HEAP SUMMARY:
==17507==     in use at exit: 0 bytes in 0 blocks
==17507==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==17507==
==17507== All heap blocks were freed -- no leaks are possible
==17507==
==17507== For counts of detected and suppressed errors, rerun with: -v
==17507== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Illegal instruction