Abort libprocess when a Process throws an uncaught exception.
Abort libprocess when a Process throws an uncaught exception.

Previously, we logged the exception, terminated the throwing
Process, and continued to run. However, currently there exists
no known user-level code that I'm aware of that handles the
unexpected termination due to an uncaught exception.

Generally, this means that when an exception is thrown (e.g.
a bad call to std::map::at), the process terminates with a log
message but things get "stuck" and the user has to debug what
is wrong / kill the process.

Libprocess would likely need to provide some primitives to
better support handling unexpected termination of a Process
in order for us to provide a strategy where we continue running.

Review: https://reviews.apache.org/r/64939

chhsia0/mesos,reneploetz/mesos,jpeach/mesos,reneploetz/mesos,Gilbert88/mesos,abudnik/mesos,kaysoky/mesos,andschwa/mesos,dforsyth/mesos,chhsia0/mesos,jpeach/mesos,chhsia0/mesos,kaysoky/mesos,dforsyth/mesos,jpeach/mesos,chhsia0/mesos,kaysoky/mesos,gsantovena/mesos,dforsyth/mesos,chhsia0/mesos,dforsyth/mesos,asamerh4/mesos,abudnik/mesos,kaysoky/mesos,gsantovena/mesos,gsantovena/mesos,asamerh4/mesos,Gilbert88/mesos,jpeach/mesos,andschwa/mesos,abudnik/mesos,gsantovena/mesos,jpeach/mesos,jpeach/mesos,Gilbert88/mesos,gsantovena/mesos,dforsyth/mesos,andschwa/mesos,Gilbert88/mesos,asamerh4/mesos,reneploetz/mesos,Gilbert88/mesos,abudnik/mesos,Gilbert88/mesos,andschwa/mesos,gsantovena/mesos,kaysoky/mesos,abudnik/mesos,asamerh4/mesos,asamerh4/mesos,reneploetz/mesos,andschwa/mesos,reneploetz/mesos,andschwa/mesos,dforsyth/mesos,reneploetz/mesos,asamerh4/mesos,gsantovena/mesos,kaysoky/mesos,kaysoky/mesos,chhsia0/mesos,jpeach/mesos,asamerh4/mesos,dforsyth/mesos,chhsia0/mesos,andschwa/mesos,reneploetz/mesos,abudnik/mesos,Gilbert88/mesos,abudnik/mesos