assigning of abrt crashes

Colin Walters walters at verbum.org
Mon Aug 16 15:01:36 UTC 2010


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


More information about the devel mailing list