error 0 ==26905== Memcheck, a memory error detector ==26905== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==26905== Using Valgrind-3.15.0.GIT and LibVEX; rerun with -h for copyright info ==26905== Command: ./try ==26905== vex amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF7 0xF 0x92 0xC0 0x83 0xEA 0x1 vex amd64->IR: REX=1 REX.W=1 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=0 ==26905== valgrind: Unrecognised instruction at address 0x1120c8. ==26905== at 0x1120C8: crandom_generate (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try) ==26905== by 0x10B3A3: goldilocks_keygen (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try) ==26905== by 0x10AB12: crypto_sign_ed448goldilocks_64_keypair (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try) ==26905== by 0x109703: test (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try) ==26905== by 0x109114: main (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try) ==26905== Your program just tried to execute an instruction that Valgrind ==26905== did not recognise. There are two possible reasons for this. ==26905== 1. Your program has a bug and erroneously jumped to a non-code ==26905== location. If you are running Memcheck and you just saw a ==26905== warning about a bad jump, it's probably your program's fault. ==26905== 2. The instruction is legitimate but Valgrind doesn't handle it, ==26905== i.e. it's Valgrind's fault. If you think this is the case or ==26905== you are not sure, please let us know and we'll try to fix it. ==26905== Either way, Valgrind will now raise a SIGILL signal which will ==26905== probably kill your program. ==26905== ==26905== Process terminating with default action of signal 4 (SIGILL) ==26905== Illegal opcode at address 0x1120C8 ==26905== at 0x1120C8: crandom_generate (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try) ==26905== by 0x10B3A3: goldilocks_keygen (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try) ==26905== by 0x10AB12: crypto_sign_ed448goldilocks_64_keypair (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try) ==26905== by 0x109703: test (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try) ==26905== by 0x109114: main (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try) ==26905== ==26905== HEAP SUMMARY: ==26905== in use at exit: 44,640 bytes in 10 blocks ==26905== total heap usage: 20 allocs, 10 frees, 69,848 bytes allocated ==26905== ==26905== LEAK SUMMARY: ==26905== definitely lost: 0 bytes in 0 blocks ==26905== indirectly lost: 0 bytes in 0 blocks ==26905== possibly lost: 44,640 bytes in 10 blocks ==26905== still reachable: 0 bytes in 0 blocks ==26905== suppressed: 0 bytes in 0 blocks ==26905== Rerun with --leak-check=full to see details of leaked memory ==26905== ==26905== For lists of detected and suppressed errors, rerun with: -s ==26905== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)