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

Posted to jira@arrow.apache.org by "Rok Mihevc (Jira)" <ji...@apache.org> on 2023/01/11 07:10:03 UTC

[jira] [Updated] (ARROW-614) [C++] Use glog (or some other tool) to print stack traces in debug builds on errors

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

Rok Mihevc updated ARROW-614:
-----------------------------
    External issue URL: https://github.com/apache/arrow/issues/15361

> [C++] Use glog (or some other tool) to print stack traces in debug builds on errors
> -----------------------------------------------------------------------------------
>
>                 Key: ARROW-614
>                 URL: https://issues.apache.org/jira/browse/ARROW-614
>             Project: Apache Arrow
>          Issue Type: New Feature
>          Components: C++
>            Reporter: Wes McKinney
>            Assignee: Yuhong Guo
>            Priority: Major
>             Fix For: 0.11.0
>
>
> When an error Status is returned in a test case, we do not have a full stack trace of where the error occurred. I believe that glog provides this functionality on x86/x86_64



--
This message was sent by Atlassian Jira
(v8.20.10#820010)