-

==7460== Memcheck, a memory error detector
==7460== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==7460== Using Valgrind-3.9.0 and LibVEX; rerun with -h for copyright info
==7460== Command: echo -Rs xbps
==7460== 
vex amd64->IR: unhandled instruction bytes: 0x66 0xF 0x1B 0x4 0x24 0x66 0xF 0x1B
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=1 PFX.F2=0 PFX.F3=0
==7460== valgrind: Unrecognised instruction at address 0x4014d57.
==7460==    at 0x4014D57: _dl_runtime_resolve (in /usr/lib/ld-2.20.so)
==7460==    by 0x401865: ??? (in /usr/bin/echo)
==7460==    by 0xFFF0001E7: ???
==7460==    by 0x1B: ???
==7460==    by 0x2: ???
==7460==    by 0xFFF000576: ???
==7460==    by 0xFFF00057B: ???
==7460==    by 0xFFF00057F: ???
==7460== Your program just tried to execute an instruction that Valgrind
==7460== did not recognise.  There are two possible reasons for this.
==7460== 1. Your program has a bug and erroneously jumped to a non-code
==7460==    location.  If you are running Memcheck and you just saw a
==7460==    warning about a bad jump, it's probably your program's fault.
==7460== 2. The instruction is legitimate but Valgrind doesn't handle it,
==7460==    i.e. it's Valgrind's fault.  If you think this is the case or
==7460==    you are not sure, please let us know and we'll try to fix it.
==7460== Either way, Valgrind will now raise a SIGILL signal which will
==7460== probably kill your program.
==7460== 
==7460== Process terminating with default action of signal 4 (SIGILL)
==7460==  Illegal opcode at address 0x4014D57
==7460==    at 0x4014D57: _dl_runtime_resolve (in /usr/lib/ld-2.20.so)
==7460==    by 0x401865: ??? (in /usr/bin/echo)
==7460==    by 0xFFF0001E7: ???
==7460==    by 0x1B: ???
==7460==    by 0x2: ???
==7460==    by 0xFFF000576: ???
==7460==    by 0xFFF00057B: ???
==7460==    by 0xFFF00057F: ???
==7460== valgrind: Unrecognised instruction at address 0x4014d57.
==7460==    at 0x4014D57: _dl_runtime_resolve (in /usr/lib/ld-2.20.so)
==7460==    by 0x4A2469C: _vgnU_freeres (in /usr/lib/valgrind/vgpreload_core-amd64-linux.so)
==7460== Your program just tried to execute an instruction that Valgrind
==7460== did not recognise.  There are two possible reasons for this.
==7460== 1. Your program has a bug and erroneously jumped to a non-code
==7460==    location.  If you are running Memcheck and you just saw a
==7460==    warning about a bad jump, it's probably your program's fault.
==7460== 2. The instruction is legitimate but Valgrind doesn't handle it,
==7460==    i.e. it's Valgrind's fault.  If you think this is the case or
==7460==    you are not sure, please let us know and we'll try to fix it.
==7460== Either way, Valgrind will now raise a SIGILL signal which will
==7460== probably kill your program.
==7460== 
==7460== Process terminating with default action of signal 4 (SIGILL)
==7460==  Illegal opcode at address 0x4014D57
==7460==    at 0x4014D57: _dl_runtime_resolve (in /usr/lib/ld-2.20.so)
==7460==    by 0x4A2469C: _vgnU_freeres (in /usr/lib/valgrind/vgpreload_core-amd64-linux.so)
==7460== 
==7460== HEAP SUMMARY:
==7460==     in use at exit: 0 bytes in 0 blocks
==7460==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==7460== 
==7460== All heap blocks were freed -- no leaks are possible
==7460== 
==7460== For counts of detected and suppressed errors, rerun with: -v
==7460== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 1 from 1)