[ https://issues.apache.org/jira/browse/ARROW-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wes McKinney reassigned ARROW-2138: ----------------------------------- Assignee: Antoine Pitrou > [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 > Assignee: Antoine Pitrou > Priority: Trivial > Labels: pull-request-available > 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)