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

[Bernhard Reiter]

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.

> How to do this:
> If you build the client yourself
> this means using --enable-debug=full in the configure line.

See the manual page for "strip" in the section --only-keep-debug.

> If you access our kde35 enterprise packages for Debian Etch
> (e.g. from http://apt.intevation.de/dists/etch/experimental/),
> do not forget to install the package kdepim-dbg.
> We will add kdepim as dependency to the meta-package there shortly.

The Etch packages have this already, so there are no replacement binaries
in kdepim-dbg, but only the additional symbols for debugging.

Bernhard

-- 
Managing Director - Owner: www.intevation.net       (Free Software Company)
Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.kolab.org/pipermail/devel/attachments/20070808/9b8841ea/attachment.sig>