You must set the environment variable KDE_DEBUG (to 1 or whatever you want in fact).

You must set the environment variable KDE_DEBUG (to 1 or whatever you want in fact).

+

<!--T:4-->

To get Dr Konqi back, unset the KDE_DEBUG environment variable.

To get Dr Konqi back, unset the KDE_DEBUG environment variable.

+

<!--T:5-->

Example:<br />

Example:<br />

−

*To avoid Dr Konqi:<br />

+

*To avoid Dr Konqi:

−

::<tt>export KDE_DEBUG=1</tt>

+

::<code>export KDE_DEBUG=1</code>

−

*To see Dr Konqi:<br />

+

*To see Dr Konqi:

−

::<tt>unset KDE_DEBUG</tt>

+

::<code>unset KDE_DEBUG</code>

−

===What is a core file? How do I get a core file?===

+

===How do I switch Dr Konqi to developer mode?=== <!--T:6-->

+

<!--T:7-->

+

Edit file $KDEHOME/share/config/drkonqirc and add the following:

+

<syntaxhighlight lang="ini">

+

[drkonqi]

+

ConfigName=developer

+

</syntaxhighlight>

+

+

===What is a core file? How do I get a core file?=== <!--T:8-->

+

+

<!--T:9-->

A core file is an image of the memory when your application crashed. Using the core file, you can know which variables were set and where your application crashed.

A core file is an image of the memory when your application crashed. Using the core file, you can know which variables were set and where your application crashed.

−

Some distributions disable the generation of core files. To re-enable them, use "ulimit -c unlimited".

+

<!--T:10-->

+

Some distributions disable the generation of core files. To re-enable them, use <code>ulimit -c unlimited</code>.

−

Once you have a core file for a crash, you can examine it with gdb appname core . This will open gdb on the core file for the given application. Once at the gdb prompt, the most useful command is "bt" which generates a backtrace of the crash.

+

<!--T:11-->

−

For more information about how to use gdb, see this page.

+

Once you have a core file for a crash, you can examine it with gdb appname core . This will open gdb on the core file for the given application. Once at the gdb prompt, the most useful command is <code>bt</code> which generates a backtrace of the crash.

+

For more information about how to use gdb, see [[Special:myLanguage/Development/Tutorials/Debugging/Debugging_with_GDB|this page]]

−

===What tools are available to debug my application?===

+

===What tools are available to debug my application?=== <!--T:12-->

−

kdDebug() calls are a simple but efficient way to debug an application.

+

−

gdb, the GNU debugger, is the quickest way to execute step-by-step and investigate variables (prefer the 5.0 version, it is really better than the 4.1.x).

+

−

Valgrind

+

−

kdbg is a nice graphical frontend to gdb with a KDE GUI. It has support for many Qt types (including QString).

+

−

Memory leak tracer : See kdesdk/kmtrace. The README explains it all.

+

−

kdcop and dcop allow to browse the dcop interface and to easily make dcop calls.

+

−

Check this page and kdesdk, there are a bunch of useful scripts there.

+

−

===How do I print a QString in gdb?===

+

<!--T:13-->

−

Check out kdesdk, and add this line to your ~/.gdbinit :

+

*kDebug() (kdDebug() in KDE3) calls are a simple but efficient way to debug an application.

−

source /path/to/kde/sources/kdesdk/scripts/kde-devel-gdb

+

*gdb, the GNU debugger, is the quickest way to execute step-by-step and investigate variables (recommended versions are gdb >= 6.x)

−

Then in gdb you can do printqstring myqstring to see its contents.

+

*Valgrind

−

For instance, QString myqstring = QString::fromLatin1("contents"); can be examined using

+

*kdbg is a nice graphical frontend to gdb with a KDE GUI. It has support for many Qt types (including QString).

+

*Memory leak tracer : See kdesdk/kmtrace. The README explains it all.

+

*qdbus and dbusviewer from Qt allow to browse DBus interfaces and to easily make DBus calls.

−

(gdb) printqstring myqstring

+

<!--T:14-->

−

$1 = "content"

+

Check [[Special:myLanguage/Development/Tools|this page]] and kdesdk, there are a bunch of useful scripts there.

−

See the kde-devel-gdb file for the other macros it defines.

+

===How do I print a QString in gdb?=== <!--T:15-->

−

===I have no symbol when I debug an app that uses kpart, what should I do?===

+

<!--T:16-->

−

You must stop just after the main to load the debugging symbols of the shared library. After that, you can debug normally.

+

Check out kdesdk, and add this line to your ~/.gdbinit :

−

One can go as far as creating a gdb macro, to stop right after the part was loaded. For kword, by example, I use :

+

{{Input|1=source /path/to/kde/sources/kdesdk/scripts/kde-devel-gdb}}

+

Then in gdb you can do <code>printqstring myqstring</code> to see its contents.

+

For instance, <code>QString myqstring = QString::fromLatin1("contents");</code> can be examined using

−

define startkword

+

<!--T:17-->

−

break main

+

{{Input|1=

−

run

+

(gdb) printqstring myqstring

−

break 'KoDocument::KoDocument(int, QWidget *, char const *,

+

$1 = "content"}}

−

QObject *, char const *, bool)' cont

+

−

===How do I debug an ioslave?===

+

<!--T:18-->

+

See the <tt>kde-devel-gdb</tt> file for the other macros it defines.

−

See [[/Debugging ioslaves|debugging ioslaves]]

+

===I have no symbol when I debug an app that uses kpart, what should I do?=== <!--T:19-->

+

+

<!--T:20-->

+

You must stop just after the main to load the debugging symbols of the shared library. After that, you can debug normally.

+

One can go as far as creating a gdb macro, to stop right after the part was loaded. For kword, by example, I use:

The syntax is much like cout, you can use many native types between the "<<". This will print out a debugging message, which will automatically be turned off at release time (by --disable-debug). In case you want the message to still be there during releases, because it's a warning or an error, use kdWarning() or kdError().

+

=== Why isn't my signal and slot connection working? === <!--T:23-->

−

Components and libraries are advised to use a debug area number, as in kdDebug(1234). For this, the number must be registered in kdelibs/kdecore/kdebug.areas. Debug areas make it possible to turn off or on the debug output for specific area numbers, using the "kdebugdialog" program, which is part of kdebase. "kdebugdialog --fullmode" also permits to control where to log debug output. It is usually not necessary to register area numbers for standalone applications, unless it's so complex that you want to divide the output into several areas.

+

<!--T:24-->

+

Here are some steps that you can use to troubleshoot why your signal/slot connection is not working (your slot does not get called for some reason).

−

To make it clear: do NOT use qDebug(), this one doesn't get disabled at releases. Also avoid using assert() or kdFatal() which lead to a crash when something goes wrong, never nice for the user. Better detect the error, output a kdWarning or kdError, and recover if possible.

+

<!--T:25-->

+

1) Verify that the connect() doesn't print a warning to the console at runtime.

−

==KDE 4 specific==

+

<!--T:26-->

−

===Is there a preferred way to print debug output on stderr?===

+

If it does, check that you wrote Q_OBJECT, that the parameter names are not in the connect, that the parameter types are compatible, and that the slot is defined, and that the moc was compiled.

−

Yes, you must use kDebug():

+

−

<code cppqt>

+

<!--T:27-->

−

#include <kdebug.h>

+

1b) Or you can just check to see what connect() returns as a bool. Although this won't give you the error message.

−

kDebug() << "KMyApp just started" << endl;

+

2) Verify that the signal is indeed emitted

−

</code>

+

3) Verify that the receiver isn't already deleted at that time

+

4) Verify that emitter->signalsBlocked() returns false

−

The syntax is much like cout, you can use many native types between the "<<". This will print out a debugging message, which will automatically be turned off at release time (by --disable-debug). In case you want the message to still be there during releases, because it's a warning or an error, use kWarning() or kError().

+

===Is there a preferred way to print debug output on stderr?=== <!--T:29-->

−

Components and libraries are advised to use a debug area number, as in kDebug(1234). For this, the number must be registered in kdelibs/kdecore/kdebug.areas. Debug areas make it possible to turn off or on the debug output for specific area numbers, using the "kdebugdialog" program, which is part of kdebase. "kdebugdialog --fullmode" also permits to control where to log debug output. It is usually not necessary to register area numbers for standalone applications, unless it's so complex that you want to divide the output into several areas.

To make it clear: do NOT use qDebug(), this one doesn't get disabled at releases. Also avoid using assert() or kFatal() which lead to a crash when something goes wrong and that is not a nice experience for the user. Better detect the error, output a kWarning or kError, and recover if possible.

A core file is an image of the memory when your application crashed. Using the core file, you can know which variables were set and where your application crashed.

Some distributions disable the generation of core files. To re-enable them, use ulimit -c unlimited.

Once you have a core file for a crash, you can examine it with gdb appname core . This will open gdb on the core file for the given application. Once at the gdb prompt, the most useful command is bt which generates a backtrace of the crash.
For more information about how to use gdb, see this page

Then in gdb you can do printqstring myqstring to see its contents.
For instance, QString myqstring = QString::fromLatin1("contents"); can be examined using

(gdb) printqstring myqstring
$1 = "content"

See the kde-devel-gdb file for the other macros it defines.

[edit]I have no symbol when I debug an app that uses kpart, what should I do?

You must stop just after the main to load the debugging symbols of the shared library. After that, you can debug normally.
One can go as far as creating a gdb macro, to stop right after the part was loaded. For kword, by example, I use:

Here are some steps that you can use to troubleshoot why your signal/slot connection is not working (your slot does not get called for some reason).

1) Verify that the connect() doesn't print a warning to the console at runtime.

If it does, check that you wrote Q_OBJECT, that the parameter names are not in the connect, that the parameter types are compatible, and that the slot is defined, and that the moc was compiled.

1b) Or you can just check to see what connect() returns as a bool. Although this won't give you the error message.
2) Verify that the signal is indeed emitted
3) Verify that the receiver isn't already deleted at that time
4) Verify that emitter->signalsBlocked() returns false