On 08/17/2010 01:11 PM, drago01 wrote:
> On Mon, Aug 16, 2010 at 5:01 PM, Colin Walters wrote:
>> 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" cert
On Mon, Aug 16, 2010 at 5:01 PM, Colin Walters wrote:
> 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 whi
On Tue, 17 Aug 2010 11:20:18 -0400
Colin Walters wrote:
> On Tue, Aug 17, 2010 at 11:12 AM, Thomas Spura
> wrote:
> >
> > Without a clear way "how to reproduce" it, they can't help here
>
> One advantage of automated collection (or semi-automated like ABRT) is
> that given enough crashes, it can
On Tue, Aug 17, 2010 at 11:12 AM, Thomas Spura
wrote:
>
> Without a clear way "how to reproduce" it, they can't help here
One advantage of automated collection (or semi-automated like ABRT) is
that given enough crashes, it can be easier to track down the root
cause. So it's useful to have the re
On Tue, 17 Aug 2010 10:49:29 -0400
Colin Walters wrote:
> On Tue, Aug 17, 2010 at 6:06 AM, Thomas Spura
> wrote:
> > On Mon, 16 Aug 2010 11:01:36 -0400
> > Colin Walters wrote:
> >
> >> Hi,
> >>
> >> I'd like to propose a general rule that ABRT crash logs should
> >> remain "assigned" to the actu
On Tue, Aug 17, 2010 at 6:06 AM, Thomas Spura wrote:
> On Mon, 16 Aug 2010 11:01:36 -0400
> Colin Walters wrote:
>
>> 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
On Mon, 16 Aug 2010 11:01:36 -0400
Colin Walters wrote:
> 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
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
