|
From: Idaya N. <ida...@gm...> - 2009-07-23 09:26:16
|
Hi All, If i get a still reachable error like following =9542== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 14 from 1) ==9542== malloc/free: in use at exit: 16,884 bytes in 685 blocks. ==9542== malloc/free: 17,731 allocs, 17,046 frees, 432,033 bytes allocated. ==9542== For counts of detected errors, rerun with: -v ==9542== searching for pointers to 685 not-freed blocks. ==9542== checked 108,268 bytes. ==9542== ==9542== 428 bytes in 2 blocks are still reachable in loss record 1 of 3 ==9542== at 0x40054FB: realloc (vg_replace_malloc.c:306) ==9542== by 0x809B4A4: xrealloc (in /bin/bash) ==9542== by 0x8068D76: (within /bin/bash) ==9542== by 0x8068E19: (within /bin/bash) ==9542== by 0x8068CCA: (within /bin/bash) ==9542== by 0x8069776: print_simple_command (in /bin/bash) ==9542== by 0x806C878: (within /bin/bash) ==9542== by 0x806DC66: execute_command_internal (in /bin/bash) ==9542== by 0x806E993: execute_command_internal (in /bin/bash) ==9542== by 0x806F492: execute_command (in /bin/bash) ==9542== by 0x806E95D: execute_command_internal (in /bin/bash) ==9542== by 0x806F492: execute_command (in /bin/bash) ==9542== ==9542== ==9542== 1,870 bytes in 5 blocks are still reachable in loss record 2 of 3 ==9542== at 0x4005400: malloc (vg_replace_malloc.c:149) ==9542== by 0x809B4C7: xrealloc (in /bin/bash) ==9542== by 0x808A798: (within /bin/bash) ==9542== by 0x808A8AC: fd_to_buffered_stream (in /bin/bash) ==9542== by 0x808A8F1: with_input_from_buffered_stream (in /bin/bash) ==9542== by 0x805E926: main (in /bin/bash) ==9542== ==9542== ==9542== 14,586 bytes in 678 blocks are still reachable in loss record 3 of 3 ==9542== at 0x4005400: malloc (vg_replace_malloc.c:149) ==9542== by 0x809B529: xmalloc (in /bin/bash) ==9542== by 0x8096B68: set_default_locale (in /bin/bash) ==9542== by 0x805D870: main (in /bin/bash) ==9542== ==9542== LEAK SUMMARY: ==9542== definitely lost: 0 bytes in 0 blocks. ==9542== possibly lost: 0 bytes in 0 blocks. ==9542== still reachable: 16,884 bytes in 685 blocks. ==9542== suppressed: 0 bytes in 0 blocks. Is these errors comes from my code or in bin/bash calls, am runnig the application using the script so am getting these errors,so is the leaks because of running a shell script? Hel pme on this plz Thanks, Idhaya -- Idhaya Aricent |
|
From: Tim P. <ec...@ec...> - 2009-07-23 12:16:59
|
On Thu, 2009-07-23 at 14:56 +0530, Idaya Nirma wrote: > ==9542== LEAK SUMMARY: > ==9542== definitely lost: 0 bytes in 0 blocks. > ==9542== possibly lost: 0 bytes in 0 blocks. > ==9542== still reachable: 16,884 bytes in 685 blocks. > ==9542== suppressed: 0 bytes in 0 blocks. > > Is these errors comes from my code or in bin/bash calls, > am runnig the application using the script so am getting these > errors,so is the leaks because of running a shell script? > Hel pme on this plz Still reachable means just that, at the time the program exited, pointers to the heap blocks existed. This usually means memory allocated in main() was not freed when the program terminated, the program just relied on the OS to reclaim the memory. Its not exactly the best practice to do that, but not a 'leak' by definition. Cheers, --Tim |