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

Francois Saint-Jacques commented on ARROW-3016:
-----------------------------------------------

My comment still stands, with perf-record (and the proper flag, i.e. 
--call-graph=$unwinder_type), you can set a trigger on uprobes (a userland 
function) and it'll sample invocations to this function with the full callstack 
(plus some function parameters if you want, e.g. the size). All of this info is 
saved in the perf.data file for later post-processing with perf-script.

No need to add any code in the library.

> [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.11.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)

Reply via email to