we frequently see the same trace but from different kernel builds. This means the addresses of functions changes, but the trace is the same. For example, see bugs 785814 and bug 789518. When computing the hash, ignore the address, along with any symbols prefixed with ? We still want to see the trace, but obviously putting it in one bug rather than a new one would be more useful.
the addresses are ignored. symbols prefixed with ? are not. easy fix.
commit 90645ae8995e64816bb698599ce80e00d335f90d Author: Nikola Pajkovsky <npajkovs> Date: Tue Feb 14 14:14:20 2012 +0100 rhbz#789526 - abrt hashing on kernel backtraces needs improving Signed-off-by: Nikola Pajkovsky <npajkovs>
has this been deployed in the current versions of abrt in f16 ? bug 802532 and bug 742032 should have been auto-duped too.
not yet, but we have plan to release abrt soon.
abrt-2.0.9-1.fc17, libreport-2.0.10-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/abrt-2.0.9-1.fc17,libreport-2.0.10-1.fc17
Package abrt-2.0.9-1.fc17, libreport-2.0.10-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing abrt-2.0.9-1.fc17 libreport-2.0.10-1.fc17' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-4804/abrt-2.0.9-1.fc17,libreport-2.0.10-1.fc17 then log in and leave karma (feedback).
abrt-2.0.10-1.fc17,libreport-2.0.10-2.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/abrt-2.0.10-1.fc17,libreport-2.0.10-2.fc17
abrt-2.0.10-1.fc17, libreport-2.0.10-2.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.