[
https://issues.apache.org/jira/browse/ARROW-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16190710#comment-16190710
]
Wes McKinney commented on ARROW-614:
------------------------------------
I moved this off, as this is mostly resolved with
{{-DARROW_EXTRA_ERROR_CONTEXT}}
> [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
> Fix For: 1.0.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
(v6.4.14#64029)
