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

["Antoine Pitrou (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARROW-3016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17285938#comment-17285938 ] 

Antoine Pitrou commented on ARROW-3016:
---------------------------------------

I know [~maartenbreddels] has been experimenting with low-level profiling, perhaps he would like to take a look at this.
https://www.maartenbreddels.com/perf/jupyter/python/tracing/gil/2021/01/14/Tracing-the-Python-GIL.html


> [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: 4.0.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
(v8.3.4#803005)