Use valgrind tool (http://valgrind.org/) to check the memory leak problem. Now the valgrind can be compiled on the following platforms: X86/Linux, AMD64/Linux, PPC32/Linux, PPC64/Linux.
================= Before patching ================= # valgrind --leak-check=full --show-reachable=yes ./mem02 ............... ==8179== LEAK SUMMARY: ==8179== definitely lost: 16 bytes in 2 blocks. ==8179== possibly lost: 0 bytes in 0 blocks. ==8179== still reachable: 0 bytes in 0 blocks. ==8179== suppressed: 0 bytes in 0 blocks. =============== After patching ================== [EMAIL PROTECTED] mem]# valgrind --leak-check=full --show-reachable=yes ./mem02 ....... ==9727== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 3 from 1) ==9727== malloc/free: in use at exit: 0 bytes in 0 blocks. ==9727== malloc/free: 15,007 allocs, 15,007 frees, 1,015,968,306 bytes allocated. Signed-off-by: Jin Bing Guo <[EMAIL PROTECTED]> ----------- (See attached file: Fix_mem_leak_mem02.patch) Best regards! Jin Bing Guo 郭晋兵 Linux for System p Test IBM China Systems & Technology Laboratory in Beijing Tel: +86-10-82454439 Email: [EMAIL PROTECTED] ------------------------------------- "Do today what others won't so tomorrow you do what other's can't"
Fix_mem_leak_mem02.patch
Description: Binary data
------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
