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

Posted to dev@mesos.apache.org by "Dominic Hamon (JIRA)" <ji...@apache.org> on 2014/03/05 00:15:43 UTC

[jira] [Commented] (MESOS-1041) fatal() should use abort rather than exit(1) to get stacktraces

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

Dominic Hamon commented on MESOS-1041:
--------------------------------------

https://reviews.apache.org/r/18549/
https://reviews.apache.org/r/18550/
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)