1 The included crashreport.gdb allows for semiautomated hunting of
2 crashes. The crashlog-file will be named backtrace.log and contains all
3 the commands required to partially automate a crashlog-creation with the
6 Usage: gdb -x crashreport.gdb <executable file>
8 For creating an efficient backtrace, use -DCMAKE_BUILD_TYPE=Debug as a
9 parameter to CMake during configuration - this increases the filesize,
10 but includes all the needed information for a decent and efficient
13 -- Good luck, and happy crashhunting.