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 corresponding ways to register these signal handlers.
<br><br>If you don't have access to source code then only way that I can suggest is running from debugger.<br><br>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.
<br><br>HTH<br>Jayesh<br><br><div><span class="gmail_quote">On 9/4/07, <b class="gmail_sendername"><a href="mailto:david.hazel@enchaine.com">david.hazel@enchaine.com</a></b> <<a href="mailto:david.hazel@enchaine.com">david.hazel@enchaine.com
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">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 cause the OS to terminate the application).<br><br><br>David Hazel<br>_______________________________________________<br>maemo-developers mailing list<br><a href="mailto:maemo-developers@maemo.org">
maemo-developers@maemo.org</a><br><a href="https://lists.maemo.org/mailman/listinfo/maemo-developers">https://lists.maemo.org/mailman/listinfo/maemo-developers</a><br></blockquote></div><br>