Hi, 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 ./trace_sched -c 1 .................... ==17984== LEAK SUMMARY: ==17984== definitely lost: 3,980 bytes in 199 blocks. ==17984== possibly lost: 0 bytes in 0 blocks. ==17984== still reachable: 984 bytes in 6 blocks. ==17984== suppressed: 0 bytes in 0 blocks. ================= After patching ================= # valgrind --leak-check=full --show-reachable=yes ./trace_sched -c 1 ..................... ==29570== LEAK SUMMARY: ==29570== definitely lost: 0 bytes in 0 blocks. ==29570== possibly lost: 0 bytes in 0 blocks. ==29570== still reachable: 964 bytes in 5 blocks. ==29570== suppressed: 0 bytes in 0 blocks. Signed-off-by: Jin Bing Guo <[EMAIL PROTECTED]> ---------- (See attached file: Fix_memory_leak_trace_sched.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_memory_leak_trace_sched.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
