[drkonqi] [Bug 319886] Lower Process and I/O Priority for debugging / backtrace generation

[Richard L]

https://bugs.kde.org/show_bug.cgi?id=319886

--- Comment #2 from Richard L <richard.llom at gmail.com> ---
(In reply to comment #1)
> There is a quick trick :
> ...
Well, this looks nicer, although I could test now with only a small backtrace.

>, 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.
Here on my notebook I have "only" two cores and gdb uses both to the max ->
can't do anything else.

> 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.
Not necessarily, only when there are actually other programs are running and
using cpu time.

-- 
You are receiving this mail because:
You are the assignee for the bug.