From: Pere Pujal i Carabantes <perepujal@gm...> - 2011-12-16 18:50:53
And thanks for updating the translation of the website.
El dv 16 de 12 de 2011 a les 09:58 -0800, en/na Mohammed::Nafees va
> I need help with analyzing TuxPaint with Valgrind. I need full info.
> Thank You
Basically you need to need to compile tuxpaint without optimization (-O
0) and with debugging symbols(-g), then run it under valgrind, and after
close, inspect the output of valgrind looking for things that we may
have forgot to free, then mark them in the source files.
make clean&&make CFLAGS="-O0 -g"&&su -c"make install"
valgrind --leak-check=full --track-origins=yes
play with tuxpaint some time, then close it.
The task begins now, you should identify in valgrind-output.txt any
possible problem coming from tuxpaint, but not those ones coming from
libs, then mark it in the source files, something like
FIXME: valgrind says that abc is lacking.
Hope this helps
For those who wonder from were this mail comes:
Get latest updates about Open Source Projects, Conferences and News.