[ARROW-3016] [C++] Add ability to enable call stack logging for each memory allocation

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 8.0.0
• Component/s: C++, Documentation
• Labels: pull-request-available
• External issue URL: https://github.com/apache/arrow/issues/19377
• Assignee: Will Jones
• Reporter: Will Jones
• Created: 07/Aug/18 21:17
• Updated: 11/Jan/23 07:24
• Resolved: 03/Feb/22 13:36

Description

It is possible to gain programmatic access to the call stack in C/C++, e.g.

https://eli.thegreenplace.net/2015/programmatic-access-to-the-call-stack-in-c/

It would be valuable to have a debugging option to log the sizes of memory allocations as well as showing the call stack where that allocation is performed. In complex programs, this could help determine the origin of a memory leak

Issue Links

• relates to: ARROW-15512 [C++] OT logging for memory pool allocations
• relates to: ARROW-15408 [C++] Environment variable to turn on memory allocation logging
• links to: GitHub Pull Request #12307