[
https://issues.apache.org/jira/browse/ARROW-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wes McKinney resolved ARROW-614.
--------------------------------
Resolution: Fixed
Assignee: Yuhong Guo
Fix Version/s: (was: 1.0.0)
0.11.0
With -DARROW_EXTRA_ERROR_CONTEXT=ON and glog backtraces for other crashes, I
think we have enough logging for now
> [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
(v7.6.3#76005)
