Crash Report Data Storage

Crash reports are saved into the directory specified by the DIR name-value pair using the CDS_ERRORLOG environment variable. If DIR has not been specified, the directory name is generated by cdsGetTmpDir().

Each crash report has the default format name:

“crashReport_<DATE>_<TIME>_<SUBVERSION>_<USER>_<HOST>.log”

This can however be customized by setting the NAME_FMT name-value pair which defines the generated report name. The following keywords are used to achieve this:

%DATE = this is substituted by the current date
%TIME = this is the current time
%VERSION = this is the application version
%SUBVERSION = this is the application subversion
%PID = this is the process ID
%USER = this is the user name
%HOST = this is the host name

For example:

CDS_ERRORLOG=’NAME_FMT=crashReport_%DATE_%PID_%SUBVERSION_%USER_%HOST.log’

could generate a report name of:

/opt/reports/crashReport_180709_1014_IC6.1.4.302_jsmith_msc080.log

DIR can be set as an absolute path or as a path relative to the application startup directory.

For example:

setenv CDS_ERRORLOG ’DIR=/home/jsmith/errorlog_dir’

setenv CDS_ERRORLOG ’DIR=../<dir_name>/errorlog_dir’

There might be instances where several crash reports are generated at the same time and the timestamp is same in all these report. In such a scenario, the newly-generated crash report name is appended by a unique identifier. For example, <generated-crash-report-name>_1.log, <generated-crash-report-name>_2.log ... <generated-crash-report-name>_N.log, to avoid overwriting existing reports.

Related Topics

Crash Report Customization