Fix memory leak in time-schedule.
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 ./time-schedule
....................
==17837== LEAK SUMMARY:
==17837== definitely lost: 20,440 bytes in 1 blocks.
==17837== possibly lost: 0 bytes in 0 blocks.
==17837== still reachable: 0 bytes in 0 blocks.
==17837== suppressed: 0 bytes in 0 blocks.
=================
After patching
=================
# valgrind --leak-check=full --show-reachable=yes ./time-schedule
...................
==18224== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 3 from 1)
==18224== malloc/free: in use at exit: 0 bytes in 0 blocks.
==18224== malloc/free: 249 allocs, 249 frees, 240,112 bytes allocated.
==18224== For counts of detected errors, rerun with: -v
==18224== All heap blocks were freed -- no leaks are possible.
Signed-off-by: Jin Bing Guo <guojb@cn.ibm.com>
1 file changed