[
https://issues.apache.org/jira/browse/ARROW-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16361134#comment-16361134
]
Robert Nishihara commented on ARROW-2138:
-----------------------------------------
We did this in Ray a while back (to generate core dumps), and it was a great
change.
> [C++] Have FatalLog abort instead of exiting
> --------------------------------------------
>
> Key: ARROW-2138
> URL: https://issues.apache.org/jira/browse/ARROW-2138
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++
> Reporter: Antoine Pitrou
> Priority: Trivial
> Fix For: 0.9.0
>
>
> Not sure this is desirable, since {{util/logging.h}} was taken from glog, but
> the various debug checks current {{std::exit(1)}} on failure. This is a clean
> exit (though with an error code) and therefore doesn't trigger the usual
> debugging tools such as gdb or Python's faulthandler. By replacing it with
> something like {{std::abort()}} the exit would be recognized as a process
> crash.
>
> Thoughts?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
