[
https://issues.apache.org/jira/browse/ARROW-3016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wes McKinney updated ARROW-3016:
--------------------------------
Fix Version/s: (was: 0.12.0)
0.13.0
> [C++] Add ability to enable call stack logging for each memory allocation
> -------------------------------------------------------------------------
>
> Key: ARROW-3016
> URL: https://issues.apache.org/jira/browse/ARROW-3016
> Project: Apache Arrow
> Issue Type: New Feature
> Components: C++
> Reporter: Wes McKinney
> Priority: Major
> Fix For: 0.13.0
>
>
> 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
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
