On Tue, Sep 04, 2007 at 11:01:40PM -0700, ext Jayesh Salvi wrote:
If you end up registering your signal handlers - do only little in those
signal handlers. It's not a good idea to keep executing once you have
corrupted memory - you might run into more ugly errors.
Indeed, man signal (at least
Hi,
ext Jayesh Salvi wrote:
If you can modify application's code (at least the main() entry point) you
can register signal handlers for SIGSEGV, SIGABRT (most common causes of
program crashes) etc. Do man signal for more info. If the program is in
other languages then there should be
ext Daniel Stone [EMAIL PROTECTED] writes:
On Tue, Sep 04, 2007 at 11:01:40PM -0700, ext Jayesh Salvi wrote:
If you end up registering your signal handlers - do only little in those
signal handlers. It's not a good idea to keep executing once you have
corrupted memory - you might run into
On Wed, Sep 05, 2007 at 11:43:34AM +0300, Marius Vollmer wrote:
ext Daniel Stone [EMAIL PROTECTED] writes:
On Tue, Sep 04, 2007 at 11:01:40PM -0700, ext Jayesh Salvi wrote:
If you end up registering your signal handlers - do only little in those
signal handlers. It's not a good idea to keep
Is it possible for an application to trap abnormal termination? In other words,
can a callback be registered that will be invoked when the application is about
to be shut down because of an error that the application itself has caused
(e.g. memory allocation errors or other problems that would
