I know my engine is leaking some memory and I'm about to fix it, but I called _CrtDumpMemoryLeaks() at the end and checked the return value.
As expected, it returned TRUE but there was no "dump" of any sort. I looked over the MSDN entry - does it dump to stdout? If so, will I have to create a console (through CreateFile()) to see it in a Win32 project?
Good class architecture is not like a Swiss Army Knife; it should be more like a well balanced throwing knife.
- Mike McShaffry
Heh, you know it's funny, I fix that leak and it's still reporting TRUE.
Well I'm sure I'll figure it out where the others are eventually.
Good class architecture is not like a Swiss Army Knife; it should be more like a well balanced throwing knife.
- Mike McShaffry
The debug output window should list the memory leaks when the program exits. Something like:
Detected memory leaks!
Dumping objects ->
{112} normal block at 0x00325EA0, 20 bytes long.
Data: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD
"Think not but that I know these things; or think
I know them not: not therefore am I short
Of knowing what I ought."
-John Milton, Paradise Regained (1671)
"Work hard and it might happen."
-XSquared
What debug output window?
Good class architecture is not like a Swiss Army Knife; it should be more like a well balanced throwing knife.
- Mike McShaffry
at the very bottom fo visual studio there is a bunch of tabs, one of them is the output window. press Ctrl-Alt-O to bring it up. also you can do it through the View menu>other Windows>OutputOriginally Posted by ahluka
Founder and avid member of the Internationsl Typo Associateion
