Jump to: navigation, search

Information about the group Translation of the wiki page Development/FAQs/Debugging FAQ.
Development/FAQs/Debugging FAQCurrent message text
...ugging FAQ/Page display title/trGeliştirme/Sıkça Sorulan Sorular/Hata Ayıklama ile ilgili Sıkça Sorulan Sorular
...elopment/FAQs/Debugging FAQ/1/tr==Genel==
...elopment/FAQs/Debugging FAQ/2/tr===How do I avoid Dr Konqi?===
...elopment/FAQs/Debugging FAQ/3/trYou must set the environment variable KDE_DEBUG (to 1 or whatever you want in fact).
...elopment/FAQs/Debugging FAQ/4/trTo get Dr Konqi back, unset the KDE_DEBUG environment variable.
...elopment/FAQs/Debugging FAQ/5/trExample:<br />
*To avoid Dr Konqi:
::<code>export KDE_DEBUG=1</code>
*To see Dr Konqi:
::<code>unset KDE_DEBUG</code>
...elopment/FAQs/Debugging FAQ/6/tr===How do I switch Dr Konqi to developer mode?===
...elopment/FAQs/Debugging FAQ/7/trEdit file $KDEHOME/share/config/drkonqirc and add the following:
<syntaxhighlight lang="ini">
...elopment/FAQs/Debugging FAQ/8/tr===What is a core file? How do I get a core file?===
...elopment/FAQs/Debugging FAQ/9/trA 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.
...lopment/FAQs/Debugging FAQ/10/trSome distributions disable the generation of core files. To re-enable them, use <code>ulimit -c unlimited</code>.
...lopment/FAQs/Debugging FAQ/11/trOnce 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]]
...lopment/FAQs/Debugging FAQ/12/tr===What tools are available to debug my application?===
...lopment/FAQs/Debugging FAQ/13/tr*kDebug() (kdDebug() in KDE3) 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 (recommended versions are gdb >= 6.x)
*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.
...lopment/FAQs/Debugging FAQ/14/trCheck [[Special:myLanguage/Development/Tools|this page]] and kdesdk, there are a bunch of useful scripts there.
...lopment/FAQs/Debugging FAQ/15/tr===How do I print a QString in gdb?===
...lopment/FAQs/Debugging FAQ/16/trCheck out kdesdk, and add this line to your ~/.gdbinit :
{{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
...lopment/FAQs/Debugging FAQ/17/tr{{Input|1=
(gdb) printqstring myqstring
$1 = "content"}}
...lopment/FAQs/Debugging FAQ/18/trSee the <tt>kde-devel-gdb</tt> file for the other macros it defines.
...lopment/FAQs/Debugging FAQ/19/tr===I have no symbol when I debug an app that uses kpart, what should I do?===
...lopment/FAQs/Debugging FAQ/20/trYou 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
break 'KoDocument::KoDocument(int, QWidget *, char const *, 
                       QObject *, char const *, bool)' cont}}
...lopment/FAQs/Debugging FAQ/21/tr===How do I debug an ioslave?===
...lopment/FAQs/Debugging FAQ/22/trSee [[Development/Tutorials/Debugging/Debugging IOSlaves|debugging ioslaves]]
...lopment/FAQs/Debugging FAQ/23/tr=== Why isn't my signal and slot connection working? ===
...lopment/FAQs/Debugging FAQ/24/trHere 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).
...lopment/FAQs/Debugging FAQ/25/tr1) Verify that the connect() doesn't print a warning to the console at runtime.
...lopment/FAQs/Debugging FAQ/26/trIf 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.
...lopment/FAQs/Debugging FAQ/27/tr1b) 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
...lopment/FAQs/Debugging FAQ/28/tr==KDE 4 specific==
...lopment/FAQs/Debugging FAQ/29/tr===Is there a preferred way to print debug output on stderr?===
...lopment/FAQs/Debugging FAQ/30/trYes, you must use kDebug():
...lopment/FAQs/Debugging FAQ/31/tr<syntaxhighlight lang="cpp-qt">
#include <kdebug.h>
kDebug() << "KMyApp just started"; 
...lopment/FAQs/Debugging FAQ/32/trThe 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 <tt>--disable-debug</tt>). In case you want the message to still be there during releases, because it's a warning or an error, use <tt>kWarning()</tt> or <tt>kError()</tt>.
...lopment/FAQs/Debugging FAQ/33/trComponents 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 {{program|kdebugdialog}} program, which is part of kdebase. <tt>kdebugdialog --fullmode</tt> 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.
...lopment/FAQs/Debugging FAQ/34/trIt is possible to omit the debug area number when calling kDebug by adding the following code to your top-level CMakeLists.txt:
...lopment/FAQs/Debugging FAQ/35/tr<code>
...lopment/FAQs/Debugging FAQ/36/trFor more information, about this, see [ Allen Winter's blog post].
...lopment/FAQs/Debugging FAQ/37/trTo make it clear: do NOT use <tt>qDebug()</tt>, this one does not get disabled at releases. Also avoid using <tt>assert()</tt> or <tt>kFatal()</tt> 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 <tt>kWarning()</tt> or <tt>kError()</tt>, and recover if possible.
...lopment/FAQs/Debugging FAQ/38/trTo get timestamps with your debug output, which are useful for debugging multi-threaded, networked and asynchronous operations, <tt>export KDE_DEBUG_TIMESTAMP=1</tt> (for format 17:03:24), or <tt>export KDE_DEBUG_TIMESTAMP=2</tt> (for format 17:03:24.123) before running your app. Since KDE SC 4.5.
...lopment/FAQs/Debugging FAQ/39/tr[[Category:FAQs]]
NavigationShowing 40 messages.
KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal