|
From: Josh M. <mrl...@gm...> - 2005-02-25 03:22:58
|
If you don't insist on using that specific monitor, then Fluid Studio's memory manager is an excellent, free, and small libary that's worked wonders for me. No changes required, just use normal allocation techniques for C/C++ source code. From the website: Memory Manager (a.k.a. "MMGR") MMGR is an industrial-strength memory manager for almost any project. Not only will MMGR probably point out some bugs you never knew you had, but it is also a great development tool. Among other standard tracking tools (overruns/underruns, deallocation mismatches, etc.), MMGR also provides a rich featureset of developer tools. For example, it allows you to set a breakpoint on an arbitrary allocation, generate a snapshot report of memory currently in use, etc. You can even ask MMGR to track how much of your allocated RAM is actually in use (nothing worse than allocating 64MB of memory just to find that you only needed 2K. :) http://www.fluidstudios.com/pub/FluidStudios/MemoryManagers/Fluid_Studios_Memory_Manager.zip -Josh On Thu, 24 Feb 2005 19:13:57 -0800 (PST), Alfred P. Reaud <al...@ya...> wrote: > > Hi Y'all, > > Has anybody used the objidl.h file and associated IMalloc function? I'm at > a loss to understand how it's supposed to be used, and am trying to find > some documentation for it that makes more sense than the Microsoft site > documentation. It's part of the Microsoft Component Object Model (COM), but > all I'm needing is the memory monitoring functions. It is included in > Dev-Cpp. > > Thanks! > > > > > Alfred P. Reaud |