mesos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Hindman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-1041) fatal() should use abort rather than exit(1) to get stacktraces
Date Thu, 06 Mar 2014 19:48:46 GMT

    [ https://issues.apache.org/jira/browse/MESOS-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13922963#comment-13922963
] 

Benjamin Hindman commented on MESOS-1041:
-----------------------------------------

commit d29eec5f0f53673334d77e815283452f56a87027
Author: Dominic Hamon <dhamon@twopensource.com>
Date:   Thu Mar 6 11:46:03 2014 -0800

    Added ABORT and CHECK_* usage in Mesos.
    
    Review: https://reviews.apache.org/r/18551

> fatal() should use abort rather than exit(1) to get stacktraces
> ---------------------------------------------------------------
>
>                 Key: MESOS-1041
>                 URL: https://issues.apache.org/jira/browse/MESOS-1041
>             Project: Mesos
>          Issue Type: Improvement
>          Components: libprocess, stout
>            Reporter: Dominic Hamon
>            Assignee: Dominic Hamon
>             Fix For: 0.19.0
>
>
> exit(1) does not provide a stacktrace. abort() does.
> fatal() calls exit(1). If it used abort() it could be used in place of assert/abort everywhere
for better error messaging and stacktraces.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message