This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: ABRT unusable again
- From: fche at redhat dot com (Frank Ch. Eigler)
- To: Development discussions related to Fedora <devel at lists dot fedoraproject dot org>
- Cc: systemtap at sourceware dot org
- Date: Mon, 08 Feb 2010 11:36:23 -0500
- Subject: Re: ABRT unusable again
- References: <1265402814.2361.17.camel@wicktop.localdomain> <20100206105142.7f004d3c@faldor.intranet> <1265451794.2722.3.camel@wicktop.localdomain> <1265453594.2527.4.camel@localhost> <20100206140821.79071210@faldor.intranet>
Michael Schwendt <mschwendt@gmail.com> writes:
>> I believe ABRT shouldn't file a bug report unless it is filled in
>> properly.
>
> Yeah, some of us have pointed out that before.
> I'm happy about every detailed backtrace I get, but I would be even more
> happy if users contributed a tiny bit more and added comments to their
> tickets and responded to NEEDINFO queries and gave feedback on Test
> Updates. [...]
How much more useful would it be if ABRT had a mode where executables
that recently reported crashes are subsequently/temporarily run with
syscall tracing in the background, so that if they crash again, then
recent process syscall history can also be optionally included in an
ABRT report? This would not be hard to do with e.g. systemtap.
- FChE