Bug 541442

Summary: Semi-automatic parsing of backtrace to find most relevant part
Product: [Fedora] Fedora Reporter: Matěj Cepl <mcepl>
Component: abrtAssignee: Jiri Moskovcak <jmoskovc>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: anton, dfediuck, dvlasenk, iprikryl, jmoskovc, kklic, mcepl, mnowak, npajkovs
Target Milestone: ---Keywords: FutureFeature, Patch, Triaged
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-02-05 16:37:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Matěj Cepl 2009-11-25 22:17:52 UTC 
Description of problem:
I have developed to my jetpack script (http://git.fedorahosted.org/git/?p=triage.git;a=blob_plain;f=jetpack/bugzillaBugTriage.js;hb=jetpack look around function parseBacktrace) which parses attached backtrace and provides to the comment box most relevant part (if available). See bug 541173 comment 3 for an example. 

I guess it could be useful if abrt provided something similar automagically. Maybe shorter? How many frames are most useful?

And no, I don't think should REPLACE attaching full all-threads backtrace, just SUPPLEMENT it. The attached backtrace should remain, IMHO.
Comment 1 Denys Vlasenko 2010-02-05 16:37:57 UTC 

*** This bug has been marked as a duplicate of bug 525649 ***