Details
-
Improvement
-
Resolution: Duplicate
-
Major - P3
-
None
-
None
-
None
-
Fully Compatible
Description
By relying on these functions which do not throw on failure, we are forced to interpose our own malloc functions that call into our stack trace routines on failure.
We should standardize on the C++ new/delete API which will throw at the point of allocation failure and does not require us to use macros to change the semantics of malloc/free.
Attachments
Issue Links
- duplicates
-
SERVER-12714 Eliminate uses of realloc/malloc/free in C++ code
-
- Closed
-