Not logged in
Log in now
Create an account
Subscribe to LWN
LWN.net Weekly Edition for May 23, 2013
An "enum" for Python 3
An unexpected perf feature
LWN.net Weekly Edition for May 16, 2013
A look at the PyPy 2.0 release
Yes and no. In my experience, in some cases we end up substituting bug reports with incomplete technical information for bug reports with no engagement from the reporter.
Automated crash reporting
Posted Jun 15, 2010 23:02 UTC (Tue) by midg3t (subscriber, #30998)
I think it is going too far to expect any involvement from the user with automated crash reports. That is, after all, the whole point of automating them. The value is in collating crash reports in order to prioritize bug fixing efforts, as well as being aware of where the application is crashing so that the entire class of bugs (crashes) can be fixed. Of course Linux users are often technical enough that they will be willing to provide extra information (such as the environment and actions that produce the crash) but that should definitely be an optional step.
kerneloops.org is a good example of doing this properly.
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds