Valgrind CST Output

valgrind_cst1.txt

$valgrind --track-origins=yes ./bin/cst --o test_image.csf --i test_image.csf.ini

==12501== Memcheck, a memory error detector
==12501== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==12501== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info
==12501== Command: ./bin/cst --o test_image.csf --i test_image.csf.ini
==12501== 
==12501== Warning: client switching stacks?  SP change: 0xffefffe10 --> 0xffe7ffdf0
==12501==          to suppress, use: --max-stackframe=8388640 or greater
==12501== Invalid write of size 8
==12501==    at 0x4066E0: encryptccm (ssl_wrapper.c:72)
==12501==    by 0x404D8D: gen_auth_encrypted_data (adapt_layer_openssl.c:1059)
==12501==    by 0x40FFFA: cmd_handler_decryptdata (in /tmp/cst-3.1.0/linux64/bin/cst_encrypt)
==12501==    by 0x407E27: handle_command (in /tmp/cst-3.1.0/linux64/bin/cst_encrypt)
==12501==    by 0x40B711: yyparse (in /tmp/cst-3.1.0/linux64/bin/cst_encrypt)
==12501==    by 0x408CC2: main (in /tmp/cst-3.1.0/linux64/bin/cst_encrypt)
==12501==  Address 0xffe7ffde8 is on thread 1's stack
==12501==  in frame #0, created by encryptccm (ssl_wrapper.c:42)
==12501== 
==12501== 
==12501== Process terminating with default action of signal 11 (SIGSEGV)
==12501==  Access not within mapped region at address 0xFFE7FFDE8
==12501==    at 0x4066E0: encryptccm (ssl_wrapper.c:72)
==12501==  If you believe this happened as a result of a stack
==12501==  overflow in your program's main thread (unlikely but
==12501==  possible), you can try to increase the size of the
==12501==  main thread stack using the --main-stacksize= flag.
==12501==  The main thread stack size used in this run was 8388608.
==12501== 
==12501== Process terminating with default action of signal 11 (SIGSEGV)
==12501==  Access not within mapped region at address 0xFFE7FFDE1
==12501==    at 0x4A256B0: _vgnU_freeres (in /usr/lib/valgrind/vgpreload_core-amd64-linux.so)
==12501==  If you believe this happened as a result of a stack
==12501==  overflow in your program's main thread (unlikely but
==12501==  possible), you can try to increase the size of the
==12501==  main thread stack using the --main-stacksize= flag.
==12501==  The main thread stack size used in this run was 8388608.
==12501== 
==12501== HEAP SUMMARY:
==12501==     in use at exit: 8,496,006 bytes in 2,721 blocks
==12501==   total heap usage: 28,522 allocs, 25,801 frees, 11,350,726 bytes allocated
==12501== 
==12501== LEAK SUMMARY:
==12501==    definitely lost: 3,120 bytes in 27 blocks
==12501==    indirectly lost: 0 bytes in 0 blocks
==12501==      possibly lost: 0 bytes in 0 blocks
==12501==    still reachable: 8,492,886 bytes in 2,694 blocks
==12501==         suppressed: 0 bytes in 0 blocks
==12501== Rerun with --leak-check=full to see details of leaked memory
==12501== 
==12501== For counts of detected and suppressed errors, rerun with: -v
==12501== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)