[
https://issues.apache.org/jira/browse/ARROW-3016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17660041#comment-17660041
]
Rok Mihevc commented on ARROW-3016:
-----------------------------------
This issue has been migrated to [issue
#19377|https://github.com/apache/arrow/issues/19377] on GitHub. Please see the
[migration documentation|https://github.com/apache/arrow/issues/14542] for
further details.
> [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++, Documentation
> Reporter: Will Jones
> Assignee: Will Jones
> Priority: Major
> Labels: pull-request-available
> Fix For: 8.0.0
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> 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
(v8.20.10#820010)
