Improving Dr Konqi for developers

George Kiagiadakis at
Tue Aug 10 10:09:34 BST 2010

On Tue, Aug 10, 2010 at 12:02 PM, David Jarvie <djarvie at> wrote:
> On Mon, August 9, 2010 1:50 pm, George Kiagiadakis wrote:
>> On Mon, Aug 9, 2010 at 2:17 PM, Milian Wolff <mail at> wrote:
>>> 1) "jump to crash" button or similar. Dr Konqi is nice enough to insert
>>> [KCrash handler] in the BT, but so far I have to navigate there
>>> manually. Why
>>> not make that faster?
>> That would be useful, I have thought about that as well.
> Why not apply an initial scroll to the backtrace so that the crash is
> shown at the top when first displayed? That would avoid the need for a new
> button. My guess is that most developers will initially want to see the
> crash first anyway, so it would also save one button click/scroll action
> when it first displays. If somebody wants to see the backtrace from the
> top (as it is shown currently), it's easy to manually scroll to the top.

Well, yes, that's what I really meant. I probably didn't read well the
original proposal. I don't much like the addition of extra buttons,
but jumping to the KCrash Handler frame right after displaying the
backtrace is a very good idea.

More information about the kde-core-devel mailing list