DrKonqi 2 moved to kdereview

John Tapsell johnflux at gmail.com
Thu Apr 16 11:57:15 BST 2009

2009/4/16 George Kiagiadakis <kiagiadakis.george at gmail.com>:
> 2009/4/16 Robert Knight <robertknight at gmail.com>:
>>> * It rates the backtrace and advises the user to install debugging symbols if
>>> required and doesn't allow him to report useless backtraces.
>> What about facilities or at least hooks for automatically installing
>> the symbols or better yet, sending the report off somewhere which can
>> generate the complete backtrace automatically like Apport does on
>> Ubuntu and maybe other distributions have similar facilities?
>> The problem is that any work we require the user to do massively
>> reduces the percentage of crashes that get reported and this means
>> that developers don't know which crashes are really rare and which are
>> affecting thousands of users.  Having a button to re-generate
>> backtraces and prompting the users to install symbols themselves is an
>> incremental step but they won't really solve the problem.
> Yes, that was one of the original ideas of Darío when he first started
> working on it. However, we faced problems that we couldn't solve:
> 1) In case where we attempt to install the debugging symbols package,
> there is no standard way to find which package contains the needed
> debugging symbols. For example, if kopete crashes in kopete code, you
> need the debugging symbols for kopete. On debian, this would be the
> kdenetwork-dbg package. On arch it would be something like kopete-dbg
> (from what I was told). How can we know which package is the correct
> one?

Run a script which distros can modify.

This is how Amarok installs mp3 support etc.


More information about the kde-core-devel mailing list