[SERVER-12752] Eliminate direct uses of C allocation routines malloc, free, and realloc in the server Created: 15/Feb/14 Updated: 10/Dec/14 Resolved: 18/Feb/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Client, Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Participants: | |||||||||
| 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. |
| Comments |
| Comment by Daniel Pasette (Inactive) [ 18/Feb/14 ] |
|
duplicate of |