Quote Originally Posted by nantonop View Post
well... at the moment i'm trying to fix the leaks reported by valgrind and u can imagine some are not very easy to find... valgrind indicates the allocation spot but not where the leak actually happens
How can it possibly know where the leak happens? If it could guess that, it could write the program for you. Valgrind is a very useful tool but it's not magical.

Does valgrind report the memory as "definitely lost," "possibly lost," or what? What does the line of code look like?