Comments on: MS Visual C++ and SDL

By: Eddie

Eddie — Wed, 22 Apr 2009 08:33:05 +0000

Ah, if only I knew….

Anyhow, thanks a lot for this scrumptious tip!

By: David Roberts

David Roberts — Tue, 21 Apr 2009 16:18:06 +0000

Ah yeah, in terms of reporting the memory leaks, it will only give line/file info for malloc/free (by tracking I thought you meant detecting them to begin with)

However, I believe you can redefine new with

#define new new(_NORMAL_BLOCK, __FILE__, __LINE__)

and it will fully report the leak details. (You don’t need to do anything for delete). Note that some special/internal allocations won’t provide line/file info regardless of what you do though – I’m not sure whether STL containers full under that banner

By: Eddie

Eddie — Mon, 20 Apr 2009 21:04:50 +0000

Hm, odd, for some reason, I wasn’t able to attain the file/line number for C++ apps. Do you have any tips to get it working for C++?

By: David Roberts

David Roberts — Mon, 20 Apr 2009 16:11:56 +0000

“but for some reason, it only tracks memory C-esque leaks (such as malloc and free) but not on C++ memory allocation functions (new and delete)”

The default new handler calls malloc by default, so unless you use memory pooling, this shouldn’t make any difference.