You say that, but then, there are examples of terrible security bugs resulting from broken attempts at handling malloc failures, too.<p>The right answer is, I think:<p>* Don&#x27;t add checking code at individual malloc call-sites.<p>* If you have an allocation regime where you need to do something better than abort in response to failure, don&#x27;t use malloc directly for those allocations.<p>* Run your program with malloc rigged to blow up if it fails.