Menu
▾
▴
#1 Should be Valgrind clean
Valgrind is a tool for detecting bad memory usage, like
reading from uninitialized memory, writing outside
allocated memory or plain leaking.
Attached is a log from valgrinding Trophy. I started a
race and exited right after the starter beeps had
sounded. Running inside Valgrind, Trophy is too slow
on my system for me to ever be able to finish a
complete race.
Some of the bad memory usage comes from Clanlib, but
some of it shows problems with Trophy.
If you want to experiment with Valgrind yourselves, it
is GPLed and can be downloaded from
"http://developer.kde.org/~sewardj/".
Log from valgrinding Trophy
Logged In: YES
user_id=131866
This is with Trophy 1.1.
Logged In: YES
user_id=131866
Raise priority because the memory leaks crash the game after
five races or so.