Debugging Memory Errors with Custom Allocators
By Cristian Vlasceanu, April 01, 2002
Allocators may be weird, but it's a Good Weird. With a little help from your operating system, they can even find memory access errors.
April 2002/Debugging Memory Errors with Custom Allocators/Listing 6
// Memory access modes
enum AccessMode
memNoAccess,
memReadOnly,
memReadWrite
};
/**
* Abstract interface for a memory
* manager class that keeps track of
* the allocated memory blocks.
* Memory blocks are described by
* their start address and length.
*/
class MemMgr
{
public:
virtual ~MemMgr() {}
// Sets access mode for
// all managed memory blocks
virtual void setAccessMode(AccessMode) = 0;
// Inserts block info into the
// internal list of mem blocks
virtual void insert(const void*, size_t) = 0;
// Remove memory block info
virtual void erase(const void*, size_t) = 0;
// More methods not shown here
// ...
//
};
— End of Listing —
