[Kolab-devel] Client tests: please use full debugging mode

[David Faure]

On Wednesday 08 August 2007, Bernhard Reiter wrote:
> On Tuesday 07 August 2007 17:42, Bernhard Reiter wrote:
> > For all those that help us testing the KDE Kolab Clients (aka KDE Kontact):
> >
> > If you report problems please make sure
> > that you have  the debugging information build in and installed.
> > Even for production system we recommend to install with full debugging.
> > and possibly switch off some loglevels via kdebugdialog.
> > This will add some size to disc and memory, also speed will be a bit
> > slower, but should in a rare case the application crash, you have a lot
> > more to start your support on.
> 
> Note: Actually I do not how if any speed is lost at all, when the method
> is used of seperating a binary and its debug information into two files.

The debug symbols only take disk space, but --enable-debug=full disables
optimizations (and enables debug output), so the binaries will be slower for sure.
A better compromise is --enable-debug=yes (which leads to -O2 -g).

-- 
David Faure, faure at kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).