[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: drkonqi crashes
From:       johnflux () gmail ! com
Date:       2006-11-21 14:22:49
Message-ID: 43d8ce650611210622v734906a5vb76cef13273057b9 () mail ! gmail ! com
[Download RAW message or body]

Sorry I don't quite follow.

Why would you want to disable the backtrace if the bugAddress is
submit@bugs.kde.org ?  Isn't the solution to make sure there's always
a m_lineedit?

John

On 20/11/06, André Wöbbeking <Woebbeking@kde.org> wrote:
> Hi,
>
> today I had a crash in Konqueror and drkonqi came up. I tried "Bug
> report" and in the following dialog "Include Backtrace" I pressed the
> button "Generate". After some time of generating the backtrace drkonqi
> crashed (just disappeared without another message).
>
> This is caused by kdebase/drkonqi/toplevel.cpp line 202:
>
>   m_bugreport->setText(buf);
>
> which is:
>
> void DrKBugReport::setText(const QString &str)
> {
>   m_lineedit->setText(str);
>   m_startstring = str.simplifyWhiteSpace();
> }
>
> The problem is that m_lineedit is 0. This happens if
> KAboutData::bugAddress() == "submit@bugs.kde.org"
> (the default).
>
> Shouldn't the dialog "Include Backtrace" be skipped in this case?
>
>
> Cheers,
> André
>

[prev in list] [next in list] [prev in thread] [next in thread]