# Troubleshooting

Crash Analysis |

Both Windows and UNIX/Linux versions of PxPlus 2016 (and later) contain logic to trap unexpected application failures. When an unexpected crash occurs, the system wrap up logic will output key application information to the log file, if present.

The information reported consists of the following:

- Cause of the failure (GPF, Segmentation fault, Invalid instruction, TERM request)
- ERR, CTL, RET, LFA and LFO
- Last path accessed
- Program stack with line number and program name
- List of open files
- ERR information including error history, if enabled
- Jump history, if enabled
- Stack dump (Linux Only)

Setting the log file can be done by using any of the following options:

- 'OPTION'("LOGFILE","path") mnemonic (see 'OPTION' mnemonic)
- SETDEV (0) SET "LogFile" TO "PATH" (see SETDEV SET directive)
- Inclusion of a LOGFILE= in the [Config] section of the Windows INI file (see INI Contents)

When defining the log file, you can specify the maximum file size (in megabytes) that you want the log file to grow. See PxPlus Log File.

(The ability to define the maximum log file size was added in PxPlus 2022.)

#### Note:
On UNIX/Linux, the log file defaults to pvxtrace.log, if present.