Difference between revisions of "How to debug for reporting"

From Scribus Wiki
Jump to navigation Jump to search
Line 24: Line 24:
  
 
If you compile yourself scribus -- and you plan to report bugs -- you should enable the debugging at compile time:
 
If you compile yourself scribus -- and you plan to report bugs -- you should enable the debugging at compile time:
* if you use the autotools (<code>configure; make; make install</code>) you do it at configure time: <code>$configure --enable-debug</code>
+
* if you use the autotools (<code>configure; make; make install</code>) you can do it at configure time: <code>$configure --enable-debug</code>

Revision as of 12:00, 6 December 2006

This article is part of the HOWTOs series.
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
$

If you compile yourself scribus -- and you plan to report bugs -- you should enable the debugging at compile time:

  • if you use the autotools (configure; make; make install) you can do it at configure time: $configure --enable-debug