error 0
 crypto_encrypt_open does not handle c=t overlap
 ==6124== Memcheck, a memory error detector
 ==6124== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
 ==6124== Using Valgrind-3.15.0.GIT and LibVEX; rerun with -h for copyright info
 ==6124== Command: ./try
 ==6124==
 ==6124== Conditional jump or move depends on uninitialised value(s)
 ==6124==    at 0x4C32734: __memcmp_sse4_1 (vg_replace_strmem.c:1112)
 ==6124==    by 0x40183E: test (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try)
 ==6124==    by 0x4024C0: main (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try)
 ==6124==  Uninitialised value was created by a stack allocation
 ==6124==    at 0x406680: crypto_symenc_decrypt (in /home/moritz/Uni/2015-2016/research-internship/letstrythisagain/supercop-20181113/bench/venus/work/compile/try)
 ==6124==
 ==6124==
 ==6124== HEAP SUMMARY:
 ==6124==     in use at exit: 11,266,992 bytes in 12 blocks
 ==6124==   total heap usage: 2,118 allocs, 2,106 frees, 11,375,744 bytes allocated
 ==6124==
 ==6124== LEAK SUMMARY:
 ==6124==    definitely lost: 0 bytes in 0 blocks
 ==6124==    indirectly lost: 0 bytes in 0 blocks
 ==6124==      possibly lost: 11,266,560 bytes in 10 blocks
 ==6124==    still reachable: 432 bytes in 2 blocks
 ==6124==         suppressed: 0 bytes in 0 blocks
 ==6124== Rerun with --leak-check=full to see details of leaked memory
 ==6124==
 ==6124== For lists of detected and suppressed errors, rerun with: -s
 ==6124== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)