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 ./mallocstress -l 10 ==24547== LEAK SUMMARY: ==24547== definitely lost: 240 bytes in 1 blocks. ==24547== possibly lost: 0 bytes in 0 blocks. ==24547== still reachable: 1,024 bytes in 1 blocks. ==24547== suppressed: 0 bytes in 0 blocks. =============== After patching ================== # valgrind --leak-check=full --show-reachable=yes ./mallocstress -l 10 -t 10 ................... ==25994== LEAK SUMMARY: ==25994== definitely lost: 0 bytes in 0 blocks. ==25994== possibly lost: 0 bytes in 0 blocks. ==25994== still reachable: 1,024 bytes in 1 blocks. ==25994== suppressed: 0 bytes in 0 blocks. Signed-off-by: Jin Bing Guo <[EMAIL PROTECTED]> ----------- (See attached file: Fix_mem_leak_mallocstress.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_mallocstress.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
