Amarok Crash Handler to KDE?
Sébastien Laoût
slaout at linux62.org
Mon Jun 19 00:06:49 UTC 2006
Hello,
I'm the developer of BasKet Note Pads.
For its next version, I've used your nice custom crash handler.
That's a very good way to get more bug reports... I do hope ;-)
I think this crash handler would be useful to a lot of applications.
Why not include it in KDE 4?
Perhapse not as the standard handler, but as an alternative.
Of course, with all Amarok-dependant code removed, and made modular for Amarok
to be able to plug its own stuff.
Is it on the plan?
And also, some drawbacks need to be addressed. Like calling DrKonquy if the
backtrace is useless, instead of saying nothing to the user.
One drawback of the current DrKonquy is that it's well too technical, and it's
a too big window saying "Hey! I've crashed, cool, look at me" :-)
The Amarok crash handle is also a bit technical: the backtrace is shown
directly at the user.
A better way, I think, would be a simple window telling the application
terminated unexpectingly, with a button "Report the bug": then the user enter
a description and it is send to an HTTP server (to avoid to configure a SMTP
server, figure out one from a mail client, trying to avoid firewalls)...
And why not, the HTTP server could look at previous backtraces to find
similarities and potentialy reply to the user "This crash has been solved in
the version X.Y. You can download it here.".
Of course, developers could display the "full version" with backtrace and link
to KDevelop, but casual KDE users are not developers, so they do not have to
read backtraces.
What do you think about that?
Best regards,
Sébastien Laoût.
More information about the Amarok
mailing list