You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@arrow.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/01/31 22:14:00 UTC

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

     [ https://issues.apache.org/jira/browse/ARROW-3016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated ARROW-3016:
----------------------------------
    Labels: pull-request-available  (was: )

> [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: Wes McKinney
>            Assignee: Will Jones
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  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.1#820001)