mesos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Mahler (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MESOS-1041) fatal() should use abort rather than exit(1) to get stacktraces
Date Tue, 25 Feb 2014 23:37:19 GMT

     [ https://issues.apache.org/jira/browse/MESOS-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Benjamin Mahler updated MESOS-1041:
-----------------------------------

    Component/s: stout

Just added a 'stout' component so we can tag tickets accordingly!

> 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.1.5#6160)

Mime
View raw message