tutorials:troubleshooting:coredumpfile
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| tutorials:troubleshooting:coredumpfile [2021/04/29 06:21] – [How do get a core file] miconda | tutorials:troubleshooting:coredumpfile [2021/04/29 06:22] (current) – miconda | ||
|---|---|---|---|
| Line 6: | Line 6: | ||
| After a crash of the server it may generate a core file in its working directory, if the functionality is not disabled. This core file can be used to get the cause (or at least a hint) of the crash. The core file contains the memory of the process at the moment it crashes as well as the execution trace, so it could contain sensitive data. | After a crash of the server it may generate a core file in its working directory, if the functionality is not disabled. This core file can be used to get the cause (or at least a hint) of the crash. The core file contains the memory of the process at the moment it crashes as well as the execution trace, so it could contain sensitive data. | ||
| - | ===== Potential | + | ===== Potential |
| * Invalid input data, e.g. some messages or from the database | * Invalid input data, e.g. some messages or from the database | ||
| * Errors in the program code, e.g. null pointer access | * Errors in the program code, e.g. null pointer access | ||
| - | ===== What to do with a core file ===== | + | ===== Analyze Core File ===== |
| Core files can be examined with **gdb**, the GNU debugger. It can read the crash informations, | Core files can be examined with **gdb**, the GNU debugger. It can read the crash informations, | ||
tutorials/troubleshooting/coredumpfile.1619677308.txt.gz · Last modified: 2021/04/29 06:21 by miconda