[PATCH] drkonqi: s/backtrace/backtrace full/g

Dominique Devriese dominique.devriese at student.kuleuven.ac.be
Tue Jan 27 11:26:56 GMT 2004

Lubos Lunak writes:

> On Friday 23 of January 2004 16:48, Dominique Devriese wrote:
>> Hi,
>> I recently became aware of the existence of the gdb "backtrace
>> full" command.  This prints local stack variables in addition to
>> function arguments.  This patch makes drkonqi invoke "backtrace
>> full" instead of simply "backtrace" (or "bt" ).  I'm not sure this
>> is portable, but I'm also not sure whether drkonqi should work with
>> more than one debugger.
>> What do you think ?

>  I like it. But the backtrace itself can become not very visible if
>  there are
> many variables. I think it would be better to do "bt" followed by
> "backtrace full".

That's a good idea.  I think it also solves the problem of possible
non-gdb debuggers not supporting "backtrace full" since they would
only give an error on the second backtrace attempt, and there would
still be a useful backtrace generated.

I'm including a second patch which
1 fixes a very stupid bug with me passing the wrong count to write :(
2 implements Lubos' suggestion.

I'm going to commit this to HEAD unless someone objects.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: kdebase-drkonqi.patch
Type: text/x-patch
Size: 890 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20040127/05c14a22/attachment.bin>

More information about the kde-core-devel mailing list