Hello all,
during the time i learn C++, iam always using a memory debugger (valgrind on Linux, Dr. Memory on Win) when iam using dynamic allocations in C++. Today i tryd out using Dr. Memory with the SFML Tutorial Example and getting a lots of leaks:
ERRORS FOUND:
2 unique, 2 total unaddressable access(es)
863 unique, 916 total uninitialized access(es)
867 unique, 1523 total invalid heap argument(s)
0 unique, 0 total GDI usage error(s)
0 unique, 0 total warning(s)
885 unique, 1543 total, 353150 byte(s) of leak(s)
272 unique, 729 total, 3190617 byte(s) of possible leak(s)
ERRORS IGNORED:
6010 still-reachable allocation(s)
it seems it makes not much sense using a memory debugger during programming with SFML - or? Because its not possible to figure here some memory leaks out.
What you think ?
Use this
http://vld.codeplex.com/
honestly the best 1 I have ever used, not had 1 single false positive yet!
Just link it to your project and
//Include MemoryLeak Detector.
#if _DEBUG
#include <vld.h>
#endif
Use this
http://vld.codeplex.com/
honestly the best 1 I have ever used, not had 1 single false positive yet!
Just link it to your project and
//Include MemoryLeak Detector.
#if _DEBUG
#include <vld.h>
#endif
Thanks, but it seems not to work.
He didnt recognizing here any leak by creating sth via. new without delete.
int *mField;
mField = new int(55);
// delete mField;