[
https://issues.apache.org/jira/browse/ARROW-3016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575636#comment-16575636
]
Francois Saint-Jacques edited comment on ARROW-3016 at 8/10/18 1:13 AM:
------------------------------------------------------------------------
You can already achieve this on linux with perf and uprobe, see
[http://www.brendangregg.com/blog/2015-06-28/linux-ftrace-uprobe.html]. All you
need is debug symbols. I tend to prefer the non-intrusive runtime approach
instead of adding one more library as a dependency.
was (Author: fsaintjacques):
You can already achieve this on linux with perf and uprobe, see
[http://www.brendangregg.com/blog/2015-06-28/linux-ftrace-uprobe.html.] All you
need is debug symbols. I tend to prefer the non-intrusive runtime approach
instead of adding one more library as a dependency.
> [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)