[drkonqi] [Bug 318635] Crash assistant wizard - enter crash description before generating backtrace

Jekyll Wu adaptee at gmail.com
Sun Apr 21 21:07:42 BST 2013


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

--- Comment #2 from Jekyll Wu <adaptee at gmail.com> ---
>  then for half an hour up to several hours generates crash dump data

Are those numbers real or exaggeration ?  If real then is your harware very old
? It never takes more than 2 minutes in my 5 years old laptop to generate the
backtrace. If your hardware is not that old, you should better check your
system. Whatever, it is gdb, with the request from drkonqi, that does the real
work of generating backtrace. 

Or maybe those numbers include the downloading time of debug symbols ? 

Now back to the suggestion itself. There is good reason to generate backtrace
early. You know, not every crash is valuable enough for reporting. Even if your
system has all debug symbols available, sometimes strange crashes just happen
and gdb just can't get useful backtrace. Drkonqi will refuse to report those
kind of crashes, because they unfortunately can't provide useful information to
developers. 

Now if drkonqi first asks users to try their best to desribe the problem, then
gnerate the backtrace, and in the end tell them "the backtrace is useless so we
won't accept your report", how will those users, who have spend valuable time
in describing the crash in detail, feel about DrKonqi ?

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



More information about the Unassigned-bugs mailing list