I am actually trying to integrate the Chromium Embedded Framework(ver 3), and the JUCE Library…
At Some Point, i am able to see few memory leaks… I tried Debugging it, but it was of no help.
Then in order to know the in detailed description of the Leak(with filename and number) i used(found on some site)
#define _CRTDBG_MAP_ALLOC #include <crtdbg.h>
But this is conflicting with the HeapBlock(as it has its own definitions of malloc, calloc, etc…)
So All i Want to know if it is possible to know the filename and line number of the memory leak(some kind of macro definition i need to put in, as an extension to that of the ones already define in JUCE API), or any other way through which i can get to know the filename and line number…