You cannot enable both Just-In-Time Debugging and Core Dump concurrently.
To debug a 64-bit core dump file with a project, first ensure that your source code is built for 64-bit. In the project's properties, click
Micro Focus > Build Configuration > COBOL and click
64 bit.
(Windows)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.
Click
Run > Debug Configurations.
Click
COBOL Core Dump.
Select the configuration you want or enter a name for a new configuration.
On the
General tab, enter the following information:
COBOL Project
The project that will be used while debugging.
You can debug a core dump file without a project. You need to specify the location of the debug symbols file (.idy) on the other tabs of the debug configuration.
Core Dump File
Enter the location of where a core dump is stored. If you only specify the directory, and no core dump filename, Eclipse will prompt you for the filename when the debugger starts. The filename is
cblcore by default, but you can change this using the run-time tunable core_filename.
Executables Location
Identify a working directory. You can set this automatically to whichever directory you chose to store the core dump file.
On the
Source tab, ensure that the location of your source files is defined.
On the
Debug Symbols tab, specify the location of the debug symbols (.idy) files.
Click
Debug.
When the core dump file has been loaded, the Debug perspective is displayed, enabling you to see the state of the application at the point the core dump was created. The statement that was being executed is highlighted in an editor and the call stack is displayed in the
Debug view. Execution functions such as the step and resume functions are disabled as the application is not actually running.
