【发布时间】:2014-10-06 14:40:43
【问题描述】:
我正在运行代码,但遇到错误
* 检测到 glibc * /home/build/bin/../bin/OPENSUSE_12.2_X86_64/reader: 已损坏 双链表:0x0000000003df6dc0 *
我尝试通过 valgrind 重新运行它,以了解是否存在内存泄漏问题。我运行它作为
valgrind --leak-check=full -v ./myprog
由于程序没有完成并停止valgrind总结如下:
> ==5335== Process terminating with default action of signal 2 (SIGINT) > ==5335== at 0x54E4007: kill (in /lib64/libc-2.15.so) > ==5335== by 0x429473: ??? (in /bin/bash) > ==5335== by 0x42A313: wait_for (in /bin/bash) > ==5335== by 0x462BFE: execute_command_internal (in /bin/bash) > ==5335== by 0x463360: execute_command (in /bin/bash) > ==5335== by 0x41B7F0: reader_loop (in /bin/bash) > ==5335== by 0x41B4C9: main (in /bin/bash) > ==5335== > ==5335== HEAP SUMMARY: > ==5335== in use at exit: 37,513 bytes in 1,074 blocks > ==5335== total heap usage: 1,922 allocs, 848 frees, 72,605 bytes allocated > ==5335== > ==5335== Searching for pointers to 1,074 not-freed blocks > ==5335== Checked 220,224 bytes > ==5335== > ==5335== LEAK SUMMARY: > ==5335== definitely lost: 0 bytes in 0 blocks > ==5335== indirectly lost: 0 bytes in 0 blocks > ==5335== possibly lost: 0 bytes in 0 blocks > ==5335== still reachable: 37,513 bytes in 1,074 blocks > ==5335== suppressed: 0 bytes in 0 blocks > ==5335== Reachable blocks (those to which a pointer was found) are not shown. > ==5335== To see them, rerun with: --leak-check=full --show-reachable=yes > ==5335== > ==5335== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 2 from 2) > --5335-- > --5335-- used_suppression: 2 dl-hack3-cond-1 > ==5335== > ==5335== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 2 from 2)
在总堆使用量中:1,922 次分配,848 次释放,我想知道这里可能有什么问题吗? 但在错误摘要中没有错误。我不知道我是否应该担心代码或内存泄漏的任何问题?
【问题讨论】:
-
当你用信号杀死它时,很难分析你的程序是否正确释放它的内存,尝试自然结束它(通过达到 main 的返回)。
标签: c++ valgrind heap-memory