Valgrind/memory leak question.

Discussion in 'Mac Programming' started by Dale Cooper, Oct 11, 2009.

  1. Dale Cooper
    Expand Collapse
    macrumors regular

    Dale Cooper

    Sep 20, 2005
    I'm trying to figure out a possible memory leak in my C program. I get the following message from valgrind:

    16,020 bytes in 1 blocks are still reachable in loss record 1 of 1
    at 0x4A04B32: calloc (vg_replace_malloc.c:279)
    by 0x38932D57BF: monstartup (in /lib64/
    by 0x400B4B: __gmon_start__ (in "my app".o)
    by 0x400B6D: (within "my app".o)

    definitely lost: 0 bytes in 0 blocks.
    possibly lost: 0 bytes in 0 blocks.
    still reachable: 16,020 bytes in 1 blocks.
    suppressed: 0 bytes in 0 blocks.

    This doesn't seem to happen with any of "my" memory allocation (none of which are of 16020 bytes). Is this leak "my fault" - is there anything I can do about it? It happens quite randomly - I can try to do the excact same operation several times, and it's a 50-50 chance I'll get this error or "No leaks possible".

    Any help would be very much appreciated!

Share This Page