Core Dump Debugging

Core dump debugging enables you to see what went wrong during the execution of a program. When an error occurs or when you programmatically invoke a core dump, the operating system generates a core file. This core file contains a snapshot of the process's memory when the core dump process was generated. You can use this core file to debug the failing program on your Development Hub, or if you have the required source and .idy files, you can debug in another (remote) environment.

Note: If you do not have the source file that were directly used to build the program, you must ensure that the sources you do have are in the same state (directive settings, optimization, etc..) as they were during the initial build. Also, if moving the sources to debug, any supporting files used by the application (shared libraries, shared objects, third-party libraries, etc…) must be installed along the same path in the remote environments.

To generate a core dump, you need to call the CBL_CREATE_CORE library routine from your program, or add the run-time tunable core_on_error to your run-time configuration file. For details on the run-time configuration file and run-time tunables, see Run-time Configuration.

Note: If the tunable debug_on_error is set, the core_on_error tunable is overridden. You must therefore delete any reference to debug_on_error.

To use a core file to debug, start Character Animator, specifying the core file:

anim core-filename