[
https://issues.apache.org/jira/browse/ARROW-17311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ben Kietzman updated ARROW-17311:
---------------------------------
Description:
[https://github.com/bombela/backward-cpp] is a neat single-header library which
allows capture of very expressive stack traces. It is compatible with c++11 and
is cross platform, I think it would greatly improve error reporting in arrow.
In particular, the stack traces provided by a failed DCHECK are much less
expressive than they could be and don't include file/line information, while
the traces added to statuses by {{ARROW_EXTRA_ERROR_CONTEXT}} don't include the
frame in which the status was constructed- which is frequently the frame which
we most need information from.
was:[https://github.com/bombela/backward-cpp] is a neat single-header library
which allows capture of very expressive stack traces. It is compatible with
c++11 and is cross platform, I think it would greatly improve error reporting
in arrow. In particular, the stack traces provided by a failed DCHECK are much
less expressive than they could be and don't include file/line information,
while the traces added to statuses by {{ARROW_EXTRA_ERROR_CONTEXT}} don't
include the frame in which the status was constructed- which is frequently the
frame which we most need information from.
> [C++] Vendor backward for better stack traces
> ---------------------------------------------
>
> Key: ARROW-17311
> URL: https://issues.apache.org/jira/browse/ARROW-17311
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++
> Reporter: Ben Kietzman
> Priority: Major
>
> [https://github.com/bombela/backward-cpp] is a neat single-header library
> which allows capture of very expressive stack traces. It is compatible with
> c++11 and is cross platform, I think it would greatly improve error reporting
> in arrow.
> In particular, the stack traces provided by a failed DCHECK are much less
> expressive than they could be and don't include file/line information, while
> the traces added to statuses by {{ARROW_EXTRA_ERROR_CONTEXT}} don't include
> the frame in which the status was constructed- which is frequently the frame
> which we most need information from.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
