[
https://issues.apache.org/jira/browse/MESOS-7547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhitao Li updated MESOS-7547:
-----------------------------
Description:
Mesos uses the {{CHECK}} and {{LOG(FATAL)}} from glog extensively, but it seems
like the default behavior in glog is only log the trace to stderr instead of
generating any coredump.
It seems that the [default behavior of glog |
http://rpg.ifi.uzh.ch/docs/glog.html] is to call {{exit(1)}} which does not
produce any coredump.
However, it is possible to use {{InstallFailureFunction()}} to install a custom
failure function, which calls {{abort()}}
cc [~jamespeach]
was:
Mesos uses the {{CHECK}} and {{LOG(FATAL)}} from glog extensively, but it seems
like the default behavior in glog is only log the trace to stderr instead of
generating any coredump.
It seems that the [default behavior of glog |
http://rpg.ifi.uzh.ch/docs/glog.html] is to call {{exit(1)}} which does not
produce any coredump.
However, it is possible to use {{InstallFailureFunction()}} to install a custom
failure function.
cc [~jamespeach]
> Allow coredumps to be generated from failed CHECK
> -------------------------------------------------
>
> Key: MESOS-7547
> URL: https://issues.apache.org/jira/browse/MESOS-7547
> Project: Mesos
> Issue Type: Bug
> Reporter: Zhitao Li
>
> Mesos uses the {{CHECK}} and {{LOG(FATAL)}} from glog extensively, but it
> seems like the default behavior in glog is only log the trace to stderr
> instead of generating any coredump.
> It seems that the [default behavior of glog |
> http://rpg.ifi.uzh.ch/docs/glog.html] is to call {{exit(1)}} which does not
> produce any coredump.
> However, it is possible to use {{InstallFailureFunction()}} to install a
> custom failure function, which calls {{abort()}}
> cc [~jamespeach]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
