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

List:       kde-devel
Subject:    Re: Some thoughts and brainstorming about DrKonqui crash handler
From:       Darío Andrés <andresbajotierra () gmail ! com>
Date:       2009-02-08 17:45:14
Message-ID: a2c126ef0902080945j60e0b4f3ud3c0396371946562 () mail ! gmail ! com
[Download RAW message or body]

Something I'm working on:
Is a (preliminary draft) report (ODT) of a new crash handler dialog:

http://www.mediafire.com/?gzdsk1jcnr2

I'm attaching a link as the file is too big for the ML
Regards.
Darío

On Sat, Jan 24, 2009 at 12:00 PM, Darío Andrés
<andresbajotierra@gmail.com> wrote:
> Bad bug number: I meant bug 174078 : http://bugs.kde.org/show_bug.cgi?id=174078
>
> On Sat, Jan 24, 2009 at 11:59 AM, Darío Andrés
> <andresbajotierra@gmail.com> wrote:
>> - We need to avoid messes like http://bugs.kde.org/show_bug.cgi?id=167473
>> I suppose this is because the report title is the same as the KCrash
>> handler title. (App (appexec) crashed and caused the signal X
>> (SIGNAME). )
>> So anyone reporting an "App" crash will post in there , but the
>> backtraces, the causes and the crash itself are completely different.
>> We should encourage the user to choose an unique title for the report
>> or (probably better) to look the backtrace he got and the backtrace
>> posted and *compare* them, so  if they are a lot different he needs to
>> file a new bug report
>>
>
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

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