[
https://issues.apache.org/jira/browse/ARROW-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17657646#comment-17657646
]
Rok Mihevc commented on ARROW-614:
----------------------------------
This issue has been migrated to [issue
#15361|https://github.com/apache/arrow/issues/15361] on GitHub. Please see the
[migration documentation|https://github.com/apache/arrow/issues/14542] for
further details.
> [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)
