How to debug for reporting: Difference between revisions
Jump to navigation
Jump to search
m (→On Linux) |
|||
| Line 9: | Line 9: | ||
==On Linux== | ==On Linux== | ||
If the crash happens on a Linux machine (or generally on a unix machine with the GNU gcc compiler) you can use < | If the crash happens on a Linux machine (or generally on a unix machine with the GNU gcc compiler) you can use <code>gdb</code>. | ||
You have to first load scribus in a new gdb session and launch scribus from there. After scribus has crashed you automatically get some details about the error occured. You can get a full report with the command bt (''backtrace''). | You have to first load scribus in a new gdb session and launch scribus from there. After scribus has crashed you automatically get some details about the error occured. You can get a full report with the command bt (''backtrace''). | ||
Revision as of 11:41, 6 December 2006
| Installation • Usage • PDF issues • Imposition • Other |
Introduction
When you fill a bug about a crash, most of the time it is very helpfull if you can attach a backtrace from a debugger.
This Howto tells you how to get this informations.
On Linux
If the crash happens on a Linux machine (or generally on a unix machine with the GNU gcc compiler) you can use gdb.
You have to first load scribus in a new gdb session and launch scribus from there. After scribus has crashed you automatically get some details about the error occured. You can get a full report with the command bt (backtrace).
$ gdb scribus (gdb) run ... error reporting ... (gdb) bt ... full backtracking informations (gdb) exit $