Red Hat Bugzilla – Bug 802477
deduplication false positive
Last modified: 2012-10-26 07:16:14 EDT
Description of problem:
ABRT filed two absolutely different problems into a single Bug for GDB.
Version-Release number of selected component (if applicable):
I have no idea how to find it out.
Noticed it the first time now.
Steps to Reproduce:
Bug 738482 Comment 0:
dwarf_expr_frame_base: Assertion `framefunc != NULL' failed.
Bug 738482 Comment 13:
is_thread_state: Assertion `tp' failed.
"Assertion `tp' failed." should be filed as a new Bug.
I understand ABRT got confused by the common internal-error code of GDB.
The problem seems to be that the first three function names used for the dedup hash are identical in both backtraces.
There is not much we can do with the hash, but this should be handled better in the new deduplication which uses 8 frames for comparison.
The easy way would be to have application-specific info about crash functions.
For GDB it would be "internal_error".
The better design would be to store __attribute__((noreturn)) marker into DWARF so that ABRT can consider such marker as the crash code path start.
> Version-Release number of selected component (if applicable):
> I have no idea how to find it out.
- $ rpm -q abrt
The limitation of the deduplication using the hash is known. The ABRT server which just has been deployed should deal with this better.
libreport-2.0.12-2.fc17, abrt-2.0.11-1.fc17, btparser-0.18-2.fc17 has been submitted as an update for Fedora 17.
Package abrt-2.0.12-1.fc17, libreport-2.0.13-1.fc17, btparser-0.18-2.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.12-1.fc17 libreport-2.0.13-1.fc17 btparser-0.18-2.fc17'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
abrt-2.0.12-1.fc17, libreport-2.0.13-2.fc17, btparser-0.18-2.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
I have the same problem, see bug #870371
This is going to be fixed as part of bug #845097