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

List:       kde-bugs-dist
Subject:    [Bug 115481] Amarok shouldn't open a mail when it crashes
From:       Alexandre Oliveira <aoliveira () kdemail ! net>
Date:       2005-11-01 23:28:40
Message-ID: 20051101232840.3411.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=115481         




------- Additional Comments From aoliveira kdemail net  2005-11-02 00:28 -------
Mary Ellen Foster, one problem of the builtin crash reporting, is that the backtraces \
were often worse than gdb's. We need good backtraces, and the stacks for all threads, \
as it usually can be very usefull while debugging amaroK. The main reason, though, is \
that the automatic crash report is much easier to the general user: just add a \
comment and click on send. Or even, just click on send, it can be of some help \
anyway.

We know gdb is "a bit" cpu intensive while getting the backtraces, we know lauching \
the default mail client is something some users wouldn't like very much, but that was \
our option anyway, and I don't think we regret at all. The mail system makes us \
receive MUCH more backtraces, some of them very usefull. I've fixed MANY crashes only \
with those mails, and got valuable information that helped on debugging bugs found \
here on bugs.kde.org or reported on the channel or maillist. amaroK is a very complex \
application, and without the mails, it would be much harder to debug. So, after all, \
these system was something very positive.  I'm really sad you don't like it, but if \
it's the price for faster, better and easier debugging, I'm paying this.

The system can be improved though, we'll see what we can do.


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