You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@arrow.apache.org by "Antoine Pitrou (JIRA)" <ji...@apache.org> on 2018/02/12 16:07:00 UTC

[jira] [Created] (ARROW-2138) [C++] Have FatalLog abort instead of exiting

Antoine Pitrou created ARROW-2138:
-------------------------------------

             Summary: [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


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)