Article ID: 167733
Operator new does not throw a bad_alloc exception when it fails. It simply returns a null pointer.
Operator new does call the new handler function after it fails to procure the requested block of memory, but before it returns the null pointer. An application could install a new handler to throw a bad_alloc exception as follows:
To call new handler when malloc fails to obtain the requested block of memory, use the _set_new_mode function.
To install the new handler before your global objects are initialized, create a class that sets the new handler in its constructor and installs the old new handler in its destructor. Create a global object of that type and use the init_seg pragma to force this global object to be initialized before any of your global objects. The example below demonstrates this. It also demonstrates the use of _set_new_mode to cause a failed malloc call to generate an exception. Note that to do this, the code below must reside in its own source file. You cannot change the initializations segment more than once per translation unit (source file) with the pragma init_seg.
Operator new, as implemented by Visual C++ 5.0, ignores the function exception specification. So new(std::nothrow) still generates an exception if your new handler is installed to throw an exception as the examples above demonstrate. To change this behavior, override operator new as follows:
This is a bug in Microsoft's implementation of operator new as this in not in conformance with the ANSI C++ Standard.
For additional information, please see the following articles in the Visual C++ 5.0 online Help:
Article ID: 167733 - Last Review: June 22, 2014 - Revision: 7.0