A core dump is a memory snapshot of the application data. Runtime systems which support
the functionality automatically place a core dump on the controller in the event of
an exception error. It is stored in an <application name>.core file in the application directory.
In online mode, you can also generate a core dump explicitly if the application is currently stopped at breakpoint or if an exception has occurred. In this case, CODESYS stores the core dump file in the project directory and not on the controller.
In offline mode, you can load the core dump from the PLC to the project. Then an online view of the application is displayed with the data and values at the time of the exception.
In addition, you can call a project view of the PLC log file at the time of generating the core dump.
NOTICE
The runtime system must completely support this functionality in order to assure a correct display of variable values in the core dump view.
In the online view of the application which CODESYS created when loading the core dump into the project, menu commands are displayed as available but do not have any effect in this status. When selecting one of these commands, a message is displayed.
CAUTION
Restriction: The exception handling in the runtime system may overwrite parts of the variable values in the call stack. Therefore, the original values are lost and important information may no longer be displayed for variables in functions and methods at the time of monitoring.
For creating a project archive: If you have created a core dump explicitly by clicking “Create Core Dump”, then this option is available automatically in the archive configuration. On the other hand, if you copied the core dump from the PLC, then you can add it to a project archive only by clicking “Additional Files”. Warning: A project archive with a core dump necessarily has to include the download information. If it does not, then CODESYS cannot use the core dump later.