First of all, there were at least 4-5 topics with a similar topic on SO. I read each of them and I don't feel they really help me with this specific issue. If someone else finds a duplicate question I apologize. I've done my share of searching before I posted this, as it seems like a very common question.
I'm using Visual Studio .NET 2003 on Windows 7.
I have my own overloads of new/delete that point to my own custom calls to malloc() and free() for diagnostics. My new/delete overloads are in a header file which I've included in a few files.
The problem is, the code base is pretty much spaghetti and there is no easy way to make sure these overloads get used by everything. There are includes to third party libraries that are black-box. We also use STL everywhere.
In my tests I've found that STL is still mixing calls to my own new/delete and the standard MSVC new/delete calls.
It doesn't seem realistic to include my header file in thousands of other files, that would just take far too long. Can anyone offer some tips on how to properly and effectively overload new/delete globally so everything uses my custom memory manager?
Also add these lines:
That's not how this works. You replace the two operators, and this is done at link time. All you need to do is write a single TU that defines these operators and link it into the mix. Nobody else ever needs to know about this:
In principle, there's no need for any header files to declare these functions (
operator new
,operator delete
), since the declarations of those two functions are already hardcoded into the language, if you will. However, the namesstd
,std::bad_alloc
andstd::size_t
are not predeclared, so you will probably want to include<new>
or some other header to provide those names.In C++11 and beyond, you can alternatively use
decltype(sizeof(0))
to get the size of the first parameter in a way that doesn't require any kind of library. C++11 also has a simpler exception model without dynamic exception specifications (which were finally removed from the language entirely in C++17).