From amarok Mon Oct 29 12:56:21 2007 From: Ljubomir Simin Date: Mon, 29 Oct 2007 12:56:21 +0000 To: amarok Subject: backtraces Message-Id: <200710291356.22031.ljubomir.simin () gmail ! com> X-MARC-Message: https://marc.info/?l=amarok&m=119366261301542 Hi, I was thinking about the backtraces users send when Amarok crashes. I think that could be a good topic for a short article on the next AWN. So I'm interested in some statistics: -how many backtraces are submitted? i.e. weekly/monthly -how many of them are plain useless, and what is the percentage of the useful ones? -what are the most frequent issues, what are the reasons Amarok fails the most? xine? bad packages? shared libraries versions? database issues? smp/x86_64 problems? -maybe the most used ditro? Besides statistics, I whould explain a bit what backtraces are, why debugging info is so important, and educate readers how to make a good backtrace. I would not like to wash our dirty laundry publically (if we have any ;)), just think that might be interesting. -- Ljubomir Simin Registered Linux User #351181 _______________________________________________ Amarok mailing list Amarok@kde.org https://mail.kde.org/mailman/listinfo/amarok