Created
August 23, 2012 05:23
-
-
Save redcapital/3432925 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
==2885== Memcheck, a memory error detector | |
==2885== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al. | |
==2885== Using Valgrind-3.6.1-Debian and LibVEX; rerun with -h for copyright info | |
==2885== Command: giomm-test | |
==2885== | |
==2885== | |
==2885== HEAP SUMMARY: | |
==2885== in use at exit: 93,481 bytes in 1,693 blocks | |
==2885== total heap usage: 2,493 allocs, 800 frees, 214,414 bytes allocated | |
==2885== | |
==2885== 160 (40 direct, 120 indirect) bytes in 1 blocks are definitely lost in loss record 571 of 648 | |
==2885== at 0x4028876: malloc (vg_replace_malloc.c:236) | |
==2885== by 0x433A64C: nss_parse_service_list (nsswitch.c:626) | |
==2885== by 0x433AC59: __nss_database_lookup (nsswitch.c:167) | |
==2885== by 0x4C502F8: ??? | |
==2885== by 0x4C51A5D: ??? | |
==2885== by 0x42F1956: getpwnam_r@@GLIBC_2.1.2 (getXXbyYY_r.c:256) | |
==2885== by 0x4659695: ??? (in /lib/i386-linux-gnu/libglib-2.0.so.0.3200.0) | |
==2885== by 0x61687A6C: ??? | |
==2885== | |
==2885== LEAK SUMMARY: | |
==2885== definitely lost: 40 bytes in 1 blocks | |
==2885== indirectly lost: 120 bytes in 10 blocks | |
==2885== possibly lost: 13,975 bytes in 258 blocks | |
==2885== still reachable: 79,346 bytes in 1,424 blocks | |
==2885== suppressed: 0 bytes in 0 blocks | |
==2885== Reachable blocks (those to which a pointer was found) are not shown. | |
==2885== To see them, rerun with: --leak-check=full --show-reachable=yes | |
==2885== | |
==2885== For counts of detected and suppressed errors, rerun with: -v | |
==2885== ERROR SUMMARY: 89 errors from 89 contexts (suppressed: 69 from 13) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment