Unless your application programmatically generates a core dump, by calling the CBL_CREATE_CORE library routine, you must use run-time tunables to produce one.
set core_on_error=3 set core_filename="coredumptest.%p%t_%d"
0 | The run-time system never produces a core file on any signal or run-time system error. This is the default behavior of the run-time system. |
1 | The run-time system produces a core file when any
system signal is received that would normally produce a core file on the host system; for example, SIGBUS and SIGSEGV (which would usually produce a run-time system error 114). After writing out the core file
the process terminates immediately.
Warning: When this value is set, operating system security may prevent a core dump file from being created; refer to
Preparing for a Core Dump for instructions on how to ensure that a core dump file is created.
|
2 | The run-time system produces a core file when any run-time system error occurs. After writing out the core file the process
terminates immediately.
Warning: When this value is set, operating system security may prevent a core dump file from being created; refer to
Preparing for a Core Dump for instructions on how to ensure that a core dump file is created.
|
3 | The run-time system produces a snap shot core file when any run-time system error occurs. After writing out the core file the process continues as normal; for example, to display an RTS error message. |
path&filename | The path and name of the file that will be produced when a core file is generated if you set the core_on_error tunable to
the value 3. If
filename contains a tunable string it is substituted as follows:
|