assigning of abrt crashes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

I'd like to propose a general rule that ABRT crash logs should remain
"assigned" to the actual application, unless an actual investigation
has been done and there's a "reasonable" certainty the flaw is in the
library code in which it happened to crash.

Rationale: Applications are more likely to be buggy (I'm just
asserting this, but it seems obvious), and just because a crash
happened inside the library, particularly when C/C++ is involved,
means nothing; the flaw could still be in the application.  If we
reassign them, it's harder to make all crashes for an application
visible.

I'm fine with being added to a CC list, but reassigning is more of a mess.

Sample crash: https://bugzilla.redhat.com/show_bug.cgi?id=624098
-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux