Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 490502[details]
Proposed patch
Description of problem:
Currently the duplicate hash of a crash is computed from the package NVR (name, version, release), path of the executable, and the backtrace hash.
This is very unfortunate because the package NVR is changed with every update, and path of the executable is not a good differentiator. When multiple executables from a single component crash with similar backtrace, it is better to assume that they share code.
Version-Release number of selected component (if applicable):
1.1.16-2
Steps to Reproduce:
With abrt 1.1.16-2, you can run abrtd under gdb and
step through CAnalyzerCCpp::CreateReport (lib/Plugins/CCpp.cpp) to see how the hash is computed.
With the patch applied, you can run `abrtd -dvvv` and see the fixed hash input on abrtd's standard output.
Actual results:
Duplicate hash is computed from package nvr, executable path, and backtrace hash. Multiple crashes from older and newer package and single bug in the source code have different duplicate hashes.
Expected results:
Duplicate hash is computed from component name and backtrace hash. Multiple crashes from older and newer package and single bug in the source code have the same duplicate hash.
Comment 2RHEL Program Management
2011-04-07 09:43:45 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
This is quite important change for GSS. The hash is used for matching tickets in bugzilla with cases in customer portal. If this is not working it must be done manually and takes a lot of time to GSS engineers.
Thanks Jiri/Radek.
this change will allow us to substantially reduce triage and analysis time for roughly 50% of RHEL 6 based cases which are caused by bugs. Please reach out to me if additional detail is needed on business impact.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-0619.html
Created attachment 490502 [details] Proposed patch Description of problem: Currently the duplicate hash of a crash is computed from the package NVR (name, version, release), path of the executable, and the backtrace hash. This is very unfortunate because the package NVR is changed with every update, and path of the executable is not a good differentiator. When multiple executables from a single component crash with similar backtrace, it is better to assume that they share code. Version-Release number of selected component (if applicable): 1.1.16-2 Steps to Reproduce: With abrt 1.1.16-2, you can run abrtd under gdb and step through CAnalyzerCCpp::CreateReport (lib/Plugins/CCpp.cpp) to see how the hash is computed. With the patch applied, you can run `abrtd -dvvv` and see the fixed hash input on abrtd's standard output. Actual results: Duplicate hash is computed from package nvr, executable path, and backtrace hash. Multiple crashes from older and newer package and single bug in the source code have different duplicate hashes. Expected results: Duplicate hash is computed from component name and backtrace hash. Multiple crashes from older and newer package and single bug in the source code have the same duplicate hash.