[
https://issues.apache.org/jira/browse/MESOS-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14170686#comment-14170686
]
Adam B commented on MESOS-1870:
-------------------------------
These commits just give a line number. I believe further work is needed to get
an entire stack trace. Correct me, [~cmaloney]
> stout ABORT() should print a backtrace
> --------------------------------------
>
> Key: MESOS-1870
> URL: https://issues.apache.org/jira/browse/MESOS-1870
> Project: Mesos
> Issue Type: Bug
> Reporter: Cody Maloney
> Priority: Minor
>
> Currently we die fast and hard with little (if any) details about why we
> died. This gets particularly hard to debug around Try<>::get(), which uses a
> raw OS abort, and could be called from arbitrary surrounding code.
> Anything that is immediate process termination which we don't know to have a
> really nice, clean error message, should call stout ABORT(), which ideally
> will print a backtrace to aid with debugging.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
