Debugging Core Files Using HP WDB

core_addpid: 1 = 0

Avoiding Core File Corruption for Applications Running HP-UX 11i v3

To prevent overwriting of core files from different processes for applications running in HP-UX

11i v3, you can use the coreadm commandl.

The coreadm command enables you to specify the location and pattern for core files that are

created by abnormally terminating processes. This command can also be used to specify the path

for the core file placement. In addition, it can be used to specify the process specific pattern for

the file name of the core file.

For example, to set the global core file settings to include the process-ID and the system name

in the file name of the core, <core.pid> and to place the core file in the specified path, <path>,

you can enter the following command as a superuser at the HP-UX prompt:

# coreadm -e global -g <path>/core.%p.%n

For more information about using the coreadm command to avoid core file corruption, see

coreadm(1M)

NOTE: This feature (to prevent core file corruption) is not required for forced core-dumps. In

the case of forced core-dumps, the core files are stored in a file name, <core.pid>, by default.

Summary

WDB enables you to debug a core file and analyze the cause for the core dump. It also enables

you to force a core dump of an application and analyze the process state of the application. In

addition, you can debug a core file on a system that is different from the system on which the

core file was created.

Summary 31