[TuxKart-devel] Valgrind: more informations

[Pascal G. <pa...@gu...>]

I reran valgrind, but i "played" ~20secs.

Attached to this mail, you'll find the comnplete log.

Here's the summary:
==3134== LEAK SUMMARY:
==3134==    definitely lost: 186887 bytes in 621 blocks.
==3134==    possibly lost:   15640 bytes in 9 blocks.
==3134==    still reachable: 4863302 bytes in 86441 blocks.
==3134==         suppressed: 200 bytes in 1 blocks.
==3134== Reachable blocks (those to which a pointer was found) are not shown.
==3134== To see them, rerun with: --show-reachable=yes

Based on that (i don't know how reliable it is) either there isn't much memory
leaks (a sum of 185kb in 621 blocks isn't much) or "definitely lost: 186887
bytes in 621 blocks" means that 186887 bytes is lost 621 times, meaning ~111
Mb and we've an explanation.

Most leaks are in either /usr/lib/libplibssg.so.1.8.3 or KartDriver.cxx.

I hope this helps (and that someone will be able to interpret that information),

-Pascal
--
Projet MoviXMaker (http://sv.gnu.org/projects/movixmaker)
Projet [e]MoviX[2] (http://movix.sf.net) 
Debian Project (http://www.debian.org)
TuxKart (Wiki (GOTM): http://netpanzer.berlios.de/tuxkart/index.php)