That assumes that terminating is the correct behavior, and that everything they want to do is safe in a signal context, which it probably isn't.
-----Original Message----- From: "Daniel van Vugt" <email address hidden> Sent: 14/07/2014 18:32 To: "Daniel van Vugt" <email address hidden> Subject: Re: [Merge] lp:~vanvugt/mir/fatal-error into lp:mir/devel
I thought users could utilize the emergency recovery code?... Or maybe it needs more API still?... https://code.launchpad.net/~afrantzis/mir/platform-emergency-cleanup/+merge/222662 Inserting new handlers with that _should_ allow you to clean up on both exceptions and fatal signals.
If you relied on exceptions alone for clean up then you're missing out, because that will never catch crashes like SIGSEGV. -- https://code.launchpad.net/~vanvugt/mir/fatal-error/+merge/219471 You are reviewing the proposed merge of lp:~vanvugt/mir/fatal-error into lp:mir/devel.
« Back to merge proposal
That assumes that terminating is the correct behavior, and that everything they want to do is safe in a signal context, which it probably isn't.
-----Original Message-----
From: "Daniel van Vugt" <email address hidden>
Sent: 14/07/2014 18:32
To: "Daniel van Vugt" <email address hidden>
Subject: Re: [Merge] lp:~vanvugt/mir/fatal-error into lp:mir/devel
I thought users could utilize the emergency recovery code?... Or maybe it needs more API still?... /code.launchpad .net/~afrantzis /mir/platform- emergency- cleanup/ +merge/ 222662
https:/
Inserting new handlers with that _should_ allow you to clean up on both exceptions and fatal signals.
If you relied on exceptions alone for clean up then you're missing out, because that will never catch crashes like SIGSEGV. /code.launchpad .net/~vanvugt/ mir/fatal- error/+ merge/219471
--
https:/
You are reviewing the proposed merge of lp:~vanvugt/mir/fatal-error into lp:mir/devel.