Crash diagnosis - GoldenCheetah/GoldenCheetah GitHub Wiki

Crashes can happens due to diverse reasons: faulty hardware, bugs in device drivers and program bugs.

Crash logs are text files containing the sequence of actions conducting to the crash (the stack trace or back trace), together with the contextual information about when the crash happens, they can be useful to understand the origin of the crash and to guide the searching of a solution.

The way you can obtain a crash log depends on your Operating System:

• Windows: a crash*.log file, parallel to athlete’s folders, is automatically generated after a crash. Starting GoldenCheetah v3.6 from the File Manager, instead of from a shortcut, will include source code file names and line numbers which are relevant to understand the problem when it happens in GoldenCheetah code.

• macOS: after a crash the operating system gives you the option to see and save a crash log.

• Linux: most Linux distributions include gdb, a debugger which allows to generate a crash log, for that purpose you need to run GoldenCheetah using gdb, and use the backtrace gdb command (bt) after the crash.

Looking at the crash log it is usually possible to understand if the crash is happening in a device driver pointing to a bug there or a faulty hardware device, or in GoldenCheetah code hopefully hinting about the conditions which triggered a bug.

If you need help, please post in the users forum attaching the corresponding crash log.