KDE/FAQs/Debugging FAQ
How do I avoid Dr Konqi?
You must set the environment variable KDE_DEBUG (to 1 or whatever you want in fact).
To get Dr Konqi back, unset the KDE_DEBUG environment variable.
Example:
- To avoid Dr Konqi:
export KDE_DEBUG=1
- To see Dr Konqi:
unset KDE_DEBUG
How do I switch Dr Konqi to developer mode?
Edit file $KDEHOME/share/config/drkonqirc and add the following:
[drkonqi]
ConfigName=developer
What is a core file? How do I get a core file?
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
What tools are available to debug my application?
- KDE5 uses
qCDebug()calls to control debugging output. See Guidelines and HOWTOs/Debugging/Using Error Messages#Controlling Messages to learn how to enable output from these calls. qDebug()calls are a simple yet efficient way to debug an application; simply add aqDebug()call in the code to print e.g. the value of some variable, compile the application, then run it from a terminal emulator. The application needs to be built with debugging symbols (CMAKE_BUILD_TYPE=debug or CMAKE_BUILD_TYPE=RelWithDebInfo); if the build type is "release",qDebug()calls won't output anything- gdb, the GNU debugger, is the quickest way to execute step-by-step and investigate variables.
- Valgrind
- kdbg is a nice graphical frontend to gdb with a KDE GUI. It has support for many Qt types (including QString).
- qdbus and dbusviewer from Qt allow to browse DBus interfaces and to easily make DBus calls.
Check this page and kdesdk, there are a bunch of useful scripts there.
How do I print a QString in gdb?
Check out sdk/kde-dev-scripts, and add this line to your ~/.gdbinit :
source /path/to/kde/sources/kde/sdk/kde-dev-scripts/kde-devel-gdb
Then in gdb you can enter qs myqstring to see its contents.
For instance, QString myqstring = QString::fromLatin1("contents"); can be examined using
(gdb) qs myqstring $1 = "contents"
Look in the kde-devel-gdb file for other useful macros it defines.
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:
define startkword
break main
run
break 'KoDocument::KoDocument(int, QWidget *, char const *,
QObject *, char const *, bool)' cont
Why isn't my signal and slot connection working?
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
Is there a preferred way to print debug output on stderr?
Yes; see this tutorial.