| 1 | error 0 |
| 2 | ==26384== Memcheck, a memory error detector |
| 3 | ==26384== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. |
| 4 | ==26384== Using Valgrind-3.15.0.GIT and LibVEX; rerun with -h for copyright info |
| 5 | ==26384== Command: ./try |
| 6 | ==26384== |
| 7 | vex amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF7 0xF 0x92 0xC0 0xFF 0xCA 0xEB |
| 8 | vex amd64->IR: REX=1 REX.W=1 REX.R=0 REX.X=0 REX.B=0 |
| 9 | vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=0F |
| 10 | vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0 |
| 11 | ==26384== valgrind: Unrecognised instruction at address 0x10ecbd. |
| 12 | ==26384== at 0x10ECBD: crandom_generate (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try) |
| 13 | ==26384== by 0x10ABCB: goldilocks_keygen (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try) |
| 14 | ==26384== by 0x10A4D0: crypto_sign_ed448goldilocks_32_keypair (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try) |
| 15 | ==26384== by 0x109590: test (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try) |
| 16 | ==26384== by 0x109014: main (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try) |
| 17 | ==26384== Your program just tried to execute an instruction that Valgrind |
| 18 | ==26384== did not recognise. There are two possible reasons for this. |
| 19 | ==26384== 1. Your program has a bug and erroneously jumped to a non-code |
| 20 | ==26384== location. If you are running Memcheck and you just saw a |
| 21 | ==26384== warning about a bad jump, it's probably your program's fault. |
| 22 | ==26384== 2. The instruction is legitimate but Valgrind doesn't handle it, |
| 23 | ==26384== i.e. it's Valgrind's fault. If you think this is the case or |
| 24 | ==26384== you are not sure, please let us know and we'll try to fix it. |
| 25 | ==26384== Either way, Valgrind will now raise a SIGILL signal which will |
| 26 | ==26384== probably kill your program. |
| 27 | ==26384== |
| 28 | ==26384== Process terminating with default action of signal 4 (SIGILL) |
| 29 | ==26384== Illegal opcode at address 0x10ECBD |
| 30 | ==26384== at 0x10ECBD: crandom_generate (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try) |
| 31 | ==26384== by 0x10ABCB: goldilocks_keygen (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try) |
| 32 | ==26384== by 0x10A4D0: crypto_sign_ed448goldilocks_32_keypair (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try) |
| 33 | ==26384== by 0x109590: test (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try) |
| 34 | ==26384== by 0x109014: main (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try) |
| 35 | ==26384== |
| 36 | ==26384== HEAP SUMMARY: |
| 37 | ==26384== in use at exit: 44,640 bytes in 10 blocks |
| 38 | ==26384== total heap usage: 20 allocs, 10 frees, 67,544 bytes allocated |
| 39 | ==26384== |
| 40 | ==26384== LEAK SUMMARY: |
| 41 | ==26384== definitely lost: 0 bytes in 0 blocks |
| 42 | ==26384== indirectly lost: 0 bytes in 0 blocks |
| 43 | ==26384== possibly lost: 44,640 bytes in 10 blocks |
| 44 | ==26384== still reachable: 0 bytes in 0 blocks |
| 45 | ==26384== suppressed: 0 bytes in 0 blocks |
| 46 | ==26384== Rerun with --leak-check=full to see details of leaked memory |
| 47 | ==26384== |
| 48 | ==26384== For lists of detected and suppressed errors, rerun with: -s |
| 49 | ==26384== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) |