You can arrange for the state of an application to be saved to disk in a core dump file when the application crashes. You can then use the dump file to help debug problems, as it indicates where in the source code the error occurred, along with the values of variables, expressions, and the contents of memory as they were at the moment the error occurred.
You can produce a core dump even when you don't have the COBOL development system installed. This is valuable when you are debugging a released application on site, and you have only the
Enterprise Server environment installed.
You must have the source files and an
.idy file to get the most detail from the core dump. If you do not have the required files, you are given the name of the source file or program where the error occurred.
Note: (applies to Windows environments only)
- It is not possible to enable both Just-In-Time Debugging and Core Dump concurrently.
- To debug a 64-bit core dump you must first ensure the project is being built for 64-bit - navigate to
Micro Focus > Build Configuration > COBOL in the project's properties and click
64 bit.
- To create a core dump for an application running under IIS, the application must be run in the same user account as that being used when enabling the core dump feature. For example, a core dump will not be produced for a CGI or ISAPI application running under the default anonymous logon account.
