[drkonqi] [Bug 319886] Lower Process and I/O Priority for debugging / backtrace generation
Jekyll Wu
adaptee at gmail.com
Sun May 19 08:15:19 BST 2013
https://bugs.kde.org/show_bug.cgi?id=319886
Jekyll Wu <adaptee at gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |wishlist
--- Comment #1 from Jekyll Wu <adaptee at gmail.com> ---
There is a quick trick :
1. open /usr/share/apps/drkonqi/debuggers/internal/gdbrc
2. change the line :
"Exec=gdb -nw -n -batch -x %tempfile -p %pid %execpath"
into
"Exec=nice gdb -nw -n -batch -x %tempfile -p %pid %execpath"
However, I personally never have the feeling that drkonqi(actually, it is gdb)
is taking too much time or too much CPU resource to generate the backtrace that
it influences my normal workflow. So I can't say whether that trick will bring
noticeable change.
Also, someone reports drkonqi (again, it is actually gdb) takes too long time
to generate the backtrace. If we make drkonqi(gdb) nicer, it will takes even
longer time for that user. See bug 318635.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list