Bug 802477

Summary:	deduplication false positive
Product:	[Fedora] Fedora	Reporter:	Jan Kratochvil <jan.kratochvil>
Component:	abrt	Assignee:	abrt <abrt-devel-list>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	16	CC:	abrt-devel-list, dvlasenk, iprikryl, jakub, jan.kratochvil, jmoskovc, kklic, mlichvar, mmilata, mtoman, npajkovs, tromey, yann
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-08-30 00:57:19 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 Jan Kratochvil 2012-03-12 16:31:32 UTC

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.

How reproducible:
Noticed it the first time now.

Steps to Reproduce:
?

Actual results:
Bug 738482 Comment 0:
  ../../gdb/dwarf2loc.c:188: internal-error:
    dwarf_expr_frame_base: Assertion `framefunc != NULL' failed.
Bug 738482 Comment 13:
  ../../gdb/thread.c:623: internal-error:
    is_thread_state: Assertion `tp' failed.

Expected results:
"Assertion `tp' failed." should be filed as a new Bug.

Additional info:
I understand ABRT got confused by the common internal-error code of GDB.

Comment 1 Miroslav Lichvar 2012-03-12 16:45:12 UTC

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.

Comment 2 Jan Kratochvil 2012-03-12 17:02:00 UTC

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.

Comment 3 Jiri Moskovcak 2012-08-10 07:19:10 UTC

> 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.

Comment 4 Fedora Update System 2012-08-10 07:21:16 UTC

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.
https://admin.fedoraproject.org/updates/FEDORA-2012-11529/abrt-2.0.11-1.fc17,libreport-2.0.12-2.fc17,btparser-0.18-2.fc17

Comment 5 Fedora Update System 2012-08-23 23:28:27 UTC

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:
https://admin.fedoraproject.org/updates/FEDORA-2012-11529/abrt-2.0.12-1.fc17,libreport-2.0.13-1.fc17,btparser-0.18-2.fc17
then log in and leave karma (feedback).

Comment 6 Fedora Update System 2012-08-30 00:57:19 UTC

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.

Comment 7 Yann Droneaud 2012-10-26 11:16:14 UTC

I have the same problem, see bug #870371
This is going to be fixed as part of bug #845097