{"id":3013,"date":"2019-03-25T17:42:17","date_gmt":"2019-03-25T20:42:17","guid":{"rendered":"http:\/\/xexeu.elipse.com.br\/pt\/handling-programs-that-close-unexpectedly\/"},"modified":"2023-01-26T15:48:49","modified_gmt":"2023-01-26T18:48:49","slug":"handling-programs-that-close-unexpectedly-in-elipse-platforms","status":"publish","type":"post","link":"https:\/\/kb.elipse.com.br\/en\/handling-programs-that-close-unexpectedly-in-elipse-platforms\/","title":{"rendered":"Handling programs that close unexpectedly in Elipse platforms."},"content":{"rendered":"
\n

** This article shows how to handle programs that close unexpectedly when using Elipse platforms, especially after version 6.0. It applies to the following operating systems: Windows Vista, Windows 7, Windows 2008, and Windows 10 **<\/b><\/p>\n

Introduction<\/span><\/h2>\n

Under abnormal working conditions, some untreated exceptions in the software may occur, which may in turn cause programs to close unexpectedly for several reasons. Depending on the system, when it happens, either the application can be automatically closed or the user can be informed that the program is no longer working and will then be closed, in a message similar to the one in the figure below.<\/p>\n

\"\"
\nFigure 1: Exception\/general failure message <\/span><\/b><\/div>\n

Most of the times, to identify the exception\/failures occurring with the software (including Elipse E3 and Elipse Power), you will need Windows’s logs.<\/p>\n<\/div>\n

 <\/p>\n

Version 6.0<\/span><\/h2>\n
\n

However, from Elipse E3’s and Elipse Power’s version 6.0<\/strong> on, the default has been: E3 processes generate MiniDumps in the logs folder (C:\\eeLogs\\E3<\/em>) whenever exceptions or serious failures are detected.<\/p>\n

You can disable this behaviour via Disable process termination<\/strong> option in E3 Tweak<\/strong>. Additionally, you can set up the generation of minidump files for GPF (General Protection Failures) analyses at Configure the MiniDump<\/strong> generated option. For further information on the possible values for this option, check out Microsoft’s documentation on the subject<\/a>.<\/p>\n

<\/a><\/p>\n<\/div>\n

<\/h3>\n

Previous versions<\/span><\/h2>\n
\n

With Windows XP or other previous versions, it was possible to use DrWatson, which did not need any specific settings to record logs. With newer systems, on the other hand, although you may also count on Windows-generated logs, you will only be able to find them at WER (Windows Error Reporting), which needs specific settings to generate such logs.<\/p>\n

WER’s default behavior is to send the errors to Microsoft. However, the process of sending them to Elipse Software may take too long. Thus, the settings suggested in this article are meant to speed this process up, allowing the errors to be captured locally and the logs to be sent to Elipse.<\/p>\n

Below are the procedures for setting up the system to generate the logs.<\/p>\n

 <\/p>\n

Step 1<\/h3>\n

1. Change some values in a Windows registry key, with can be accessed via registry editor (Regedit.exe<\/span>) in:<\/p>\n

HKEY_CURRENT_USER\\Software\\Microsoft\\Windows\\Windows Error Reporting<\/span><\/p>\n

To perform these settings, just establish the values for each variable according to the two figures below. (NOTE<\/b>: neither Windows 2008 nor Vista will require the step shown in Figure 2<\/b>).<\/p>\n

\"\"
\nFigure 2: Resetting the variables’ values at WER folder <\/span><\/b>\"\"
\nFigure 3: Resetting the variables’ values at Consent folder (only for Windows 7)<\/span><\/b><\/div>\n

 <\/p>\n

The same keys inserted\/edited above need to be added to the path below:<\/p>\n

HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows\\Windows Error Reporting<\/span><\/p>\n

In some cases, E3Run’s and E3Server’s GPFs happen to SYSTEM user;
\nsince there is no user logged in the computer, the settings for a specific user may not be valid.<\/p>\n

Step 2<\/h3>\n

2. In E3 Tweak<\/strong> change the Exceptions<\/strong> key to \u201cYes\u201d.<\/p>\n<\/div>\n

Step 3<\/h3>\n

3.\u00a0 After the regedit changes, you can access the reports via Control Panel. To do so, follow one of the paths below, according to the desired system:<\/p>\n

\n