Here's some of my pet irritations with abrt. Feel free to add your own, but please keep the gratuitous "me too"ing to a minimum. 1) The generated reports contain far too little information for library owners. Consider this report: https://bugzilla.redhat.com/show_bug.cgi?id=658013 I get the EVRs for the kernel, and for the executable that happened to be running, but not for any of the libraries in between, even though the report very carefully tells me exactly which DSOs are loaded and where they are in memory. 2) I really dislike that "local trace generation" and "retrace server" are discussed as though they're the only options. If nothing else, for many non-trivial apps where abrt is potentially of the most use the core you're uploading can easily be hundreds of megabytes; that's not really better than downloading hundreds of megabytes. A network debuginfo service [1] would approach this problem in a completely different way, by letting the client download exactly as much debuginfo as it needs. 3) Reporting to bugzilla is a mistake. 4) Reporting to bugzilla without being able to scrape the bz username and password out of the firefox credential store is just cruel. [1] - http://git.fedorahosted.org/git/?p=littlebottom.git;a=summary - ajax
Attachment:
signature.asc
Description: This is a digitally signed message part
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
