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