Dolphin/FAQ/Freeze: Difference between revisions
Freininghaus (talk | contribs) (Created page with "If Dolphin freezes (i.e., it does not react any more to user input and does not repaint the window on the screen), you can do the following to help us find the cause of the pr...") |
Freininghaus (talk | contribs) No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
If Dolphin freezes (i.e., it does not react any more to user input and does not repaint the window on the screen), you can do the following to help us find the cause of the problem: | If Dolphin freezes (i.e., it does not react any more to user input and does not repaint the window on the screen), or if it keeps the CPU busy for a long time, you can do the following to help us find the cause of the problem: | ||
* Run Dolphin in GDB. In a terminal, enter | * Run Dolphin in GDB. In a terminal, enter | ||
::{{Input|1=<nowiki> | ::{{Input|1=<nowiki> | ||
| Line 6: | Line 6: | ||
::{{Input|1=<nowiki> | ::{{Input|1=<nowiki> | ||
run</nowiki>}} | run</nowiki>}} | ||
* Reproduce the freeze. | * Reproduce the freeze (or the situation in which Dolphin keeps the CPU busy for a long time). | ||
* Switch to the GDB terminal and press Control+Z. | * Switch to the GDB terminal and press Control+Z. | ||
* At the GDB prompt, enter | * At the GDB prompt, enter | ||
::{{Input|1=<nowiki> | ::{{Input|1=<nowiki> | ||
thread apply all backtrace</nowiki>}} and paste the backtrace in the bug report. | thread apply all backtrace</nowiki>}} then press Enter repeatedly until there is no further output, and paste the full backtrace in the bug report. | ||
* If the backtrace looks incomplete (i.e., there are many lines containing "??", or lines without references to .h or .cpp files and their line numbers), you can improve the quality of the backtrace by installing debug packages. See [http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports this page on KDE TechBase] for details. | * If the backtrace looks incomplete (i.e., there are many lines containing "??", or lines without references to .h or .cpp files and their line numbers), you can improve the quality of the backtrace by installing debug packages. See [http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports this page on KDE TechBase] for details. | ||
Latest revision as of 15:56, 28 July 2014
If Dolphin freezes (i.e., it does not react any more to user input and does not repaint the window on the screen), or if it keeps the CPU busy for a long time, you can do the following to help us find the cause of the problem:
- Run Dolphin in GDB. In a terminal, enter
gdb dolphin
- At the GDB prompt, enter
run
- Reproduce the freeze (or the situation in which Dolphin keeps the CPU busy for a long time).
- Switch to the GDB terminal and press Control+Z.
- At the GDB prompt, enter
thread apply all backtrace
then press Enter repeatedly until there is no further output, and paste the full backtrace in the bug report.
- If the backtrace looks incomplete (i.e., there are many lines containing "??", or lines without references to .h or .cpp files and their line numbers), you can improve the quality of the backtrace by installing debug packages. See this page on KDE TechBase for details.