Author: Anonymous Language: text
Description: No description Timestamp: 2012-09-05 08:46:09 -0400
View raw paste Reply
  1. ==16566== Memcheck, a memory error detector
  2. ==16566== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
  3. ==16566== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
  4. ==16566== Command: /usr/bin/eet -e ../../config/standard/e.cfg config e.src 1
  5. ==16566==
  6. ==16566== Invalid read of size 8
  7. ==16566==    at 0x4E40AA5: _eet_data_dump_parse (eet_data.c:3110)
  8. ==16566==    by 0x4E444B3: eet_data_undump_cipher (eet_data.c:4710)
  9. ==16566==    by 0x401E50: do_eet_encode (eet_main.c:315)
  10. ==16566==    by 0x402609: main (eet_main.c:490)
  11. ==16566==  Address 0x18 is not stack'd, malloc'd or (recently) free'd
  12. ==16566==
  13. ==16566==
  14. ==16566== Process terminating with default action of signal 11 (SIGSEGV): dumping core
  15. ==16566==  Access not within mapped region at address 0x18
  16. ==16566==    at 0x4E40AA5: _eet_data_dump_parse (eet_data.c:3110)
  17. ==16566==    by 0x4E444B3: eet_data_undump_cipher (eet_data.c:4710)
  18. ==16566==    by 0x401E50: do_eet_encode (eet_main.c:315)
  19. ==16566==    by 0x402609: main (eet_main.c:490)
  20. ==16566==  If you believe this happened as a result of a stack
  21. ==16566==  overflow in your program's main thread (unlikely but
  22. ==16566==  possible), you can try to increase the size of the
  23. ==16566==  main thread stack using the --main-stacksize= flag.
  24. ==16566==  The main thread stack size used in this run was 8388608.
  25. ==16566==
  26. ==16566== HEAP SUMMARY:
  27. ==16566==     in use at exit: 379,067 bytes in 1,770 blocks
  28. ==16566==   total heap usage: 12,278 allocs, 8,741 frees, 1,036,181 bytes allocated
  29. ==16566==
  30. ==16566== 21 bytes in 1 blocks are definitely lost in loss record 58 of 181
  31. ==16566==    at 0x4C2B6CD: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
  32. ==16566==    by 0x556A801: strdup (strdup.c:43)
  33. ==16566==    by 0x6B5CB6A: p11_kit_registered_module_to_name (in /usr/lib/x86_64-linux-gnu/libp11-kit.so.0.0.0)
  34. ==16566==    by 0x58E5574: gnutls_pkcs11_init (in /usr/lib/x86_64-linux-gnu/libgnutls.so.26.21.8)
  35. ==16566==    by 0x58CF031: gnutls_global_init (in /usr/lib/x86_64-linux-gnu/libgnutls.so.26.21.8)
  36. ==16566==    by 0x4E4B3B8: eet_init (eet_lib.c:608)
  37. ==16566==    by 0x402174: main (eet_main.c:402)
  38. ==16566==
  39. ==16566== 14,720 (192 direct, 14,528 indirect) bytes in 3 blocks are definitely lost in loss record 176 of 181
  40. ==16566==    at 0x50A91EE: _eina_chained_mempool_alloc_in (eina_chained_mempool.c:211)
  41. ==16566==    by 0x50A9438: eina_chained_mempool_malloc (eina_chained_mempool.c:300)
  42. ==16566==    by 0x4E4FC85: eina_mempool_malloc (eina_inline_mempool.x:103)
  43. ==16566==    by 0x4E4FCDB: eet_node_new (eet_node.c:24)
  44. ==16566==    by 0x4E407EA: _eet_data_dump_parse (eet_data.c:3038)
  45. ==16566==    by 0x4E444B3: eet_data_undump_cipher (eet_data.c:4710)
  46. ==16566==    by 0x401E50: do_eet_encode (eet_main.c:315)
  47. ==16566==    by 0x402609: main (eet_main.c:490)
  48. ==16566==
  49. ==16566== LEAK SUMMARY:
  50. ==16566==    definitely lost: 213 bytes in 4 blocks
  51. ==16566==    indirectly lost: 14,528 bytes in 227 blocks
  52. ==16566==      possibly lost: 0 bytes in 0 blocks
  53. ==16566==    still reachable: 253,581 bytes in 2,532 blocks
  54. ==16566==         suppressed: 64,809 bytes in 713 blocks
  55. ==16566== Reachable blocks (those to which a pointer was found) are not shown.
  56. ==16566== To see them, rerun with: --leak-check=full --show-reachable=yes
  57. ==16566==
  58. ==16566== For counts of detected and suppressed errors, rerun with: -v
  59. ==16566== ERROR SUMMARY: 3 errors from 3 contexts (suppressed: 0 from 0)
  60. [1]    16566 segmentation fault (core dumped)  valgrind --suppressions=~/.valgrind.supp --leak-check=full --show-reachable=n
  61.  
View raw paste Reply