< Development | FAQs | Debugging FAQ Revision as of 14:42, 27 June 2012 (view source)Toudidel (talk | contribs) (Created page with "===Jak mogę wyświetlić QString w gdb?===")← Older edit Revision as of 14:43, 27 June 2012 (view source) Toudidel (talk | contribs) (Created page with "Zobacz plik <tt>kde-devel-gdb</tt> z innymi makrami.")Newer edit → Line 53: Line 53: $1 = "content"}} $1 = "content"}} −See the <tt>kde-devel-gdb</tt> file for the other macros it defines. +Zobacz plik <tt>kde-devel-gdb</tt> z innymi makrami. ===I have no symbol when I debug an app that uses kpart, what should I do?=== ===I have no symbol when I debug an app that uses kpart, what should I do?=== Revision as of 14:43, 27 June 2012 Contents 1 Ogólne 1.1 Jak mogę uniknąć Dr Konqi? 1.2 Jak mogę przełączyć Dr Konqi do trybu programisty? 1.3 Co to jest plik core? Skąd wziąć plik core? 1.4 Jakich narzędzi można użyć do debuggowania mojej aplikacji? 1.5 Jak mogę wyświetlić QString w gdb? 1.6 I have no symbol when I debug an app that uses kpart, what should I do? 1.7 How do I debug an ioslave? 1.8 Why isn't my signal and slot connection working? 2 KDE 4 specific 2.1 Is there a preferred way to print debug output on stderr? Ogólne Jak mogę uniknąć Dr Konqi? Należy ustawić zmienną środowiskową KDE_DEBUG (na 1 lub jakąkolwiek inną wartość) Aby uzyskać Dr Konqi ponownie, usuń (komendą unset) zmienną środowiskową KDE_DEBUG. Przykład: Aby uniknąć Dr Konqi: export KDE_DEBUG=1 Aby zobaczyć Dr Konqi: unset KDE_DEBUG Jak mogę przełączyć Dr Konqi do trybu programisty? Edit file $KDEHOME/share/config/drkonqirc and add the following: [drkonqi] ConfigName=developer Co to jest plik core? Skąd wziąć plik core? Plik core to obraz pamięci w momencie zawieszenia aplikacji. Korzystając z pliku core, możesz poznać wartości zmiennych w momencie zawieszenia. Niektóre dystrybucje wyłączają generowanie plików core. Aby włączyć ponownie, użyj 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 Jakich narzędzi można użyć do debuggowania mojej aplikacji? 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) 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. qdbus and dbusviewer from Qt allow to browse DBus interfaces and to easily make DBus calls. Sprawdź tę stronę i kdesdk, gdzie znajdziesz masę przydatnych skryptów. Jak mogę wyświetlić QString w gdb? Check out kdesdk, and add this line to your ~/.gdbinit : source /path/to/kde/sources/kdesdk/scripts/kde-devel-gdb 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" Zobacz plik kde-devel-gdb z innymi makrami. 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 How do I debug an ioslave? See debugging ioslaves 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 KDE 4 specific Is there a preferred way to print debug output on stderr? Yes, you must use kDebug(): #include <kdebug.h> kDebug() << "KMyApp just started"; 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(). 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. It is possible to omit the debug area number when calling kDebug by adding the following code to your top-level CMakeLists.txt: add_definitions(-DKDE_DEFAULT_DEBUG_AREA=XXXX) For more information, about this, see Allen Winter's blog post. To make it clear: do NOT use qDebug(), this one does not 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. To get timestamps with your debug output, which are useful for debugging multi-threaded, networked and asynchronous operations, export KDE_DEBUG_TIMESTAMP=1 before running your app. Since KDE SC 4.5. Retrieved from "https://techbase.kde.org/index.php?title=Development/FAQs/Debugging_FAQ/pl&oldid=72361" Categories: FAQsProgramming Content is available under Creative Commons License SA 4.0 unless otherwise noted.