| | 43 | ==== Creating a backtrace ==== |
| | 44 | |
| | 45 | If you have a crash it might be useful to include a backtrace as the bug might be not reproducable on an other machine. On Unix you can create a backtrace using a core dump and gdb. A core dump is a memory dump of the state of the process when the crash happened. |
| | 46 | |
| | 47 | 1. Depending on you distribution the automatic creation of core dumps might be disabled. In that case you only see for instance {{{Segmentation fault}}} and not {{{Segmentation fault (core dumped)}}} in the shell you started QGIS from and you need to run {{{ulimit -c unlimited}}} before starting QGIS. You could also include that in your {{{.profile}}}. |
| | 48 | 1. Start {{{qgis}}} from the shell and repeat the steps to reproduce the crash. After the crash the core file will be located in the current directory. |
| | 49 | 1. To produce a backtrace from it you start {{{gdb /path/to/the/qgis/binary core}}} (e.g. the binary is usually {{{/usr/bin/qgis}}} or {{{/usr/bin/qgis.bin}}} on Debian with the GRASS plugin installed). In gdb you run {{{bt}}} which will produce the backtrace. |
