Bug 994747
Summary: | Crash report failed with latest abrt/libreport | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Adam Williamson <awilliam> |
Component: | satyr | Assignee: | Martin Milata <mmilata> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 19 | CC: | abrt-devel-list, dvlasenk, iprikryl, jfilak, jmoskovc, mikhail.v.gavrilov, mlichvar, mmilata, mtoman, stefan.home |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | satyr-0.7-1.fc18 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-09-12 01:50:56 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Adam Williamson
2013-08-07 23:59:32 UTC
satyr should always find crash thread. We had the same problem in btparser but we've fixed it. btparser commit 6a1db1e193db4136f2b170b911a946c30001fd98 Author: Martin Milata <mmilata> Date: Wed Mar 27 10:31:17 2013 +0100 Try harder when looking for crash thread The current algorithm cannot handle backtraces with multiple threads containing the designated crash frame such as [1]. We just pick the first one (from sorted threads) with the risk that our guess might be wrong. Fixes #3. [1] https://bugzilla.redhat.com/attachment.cgi?id=703269 Signed-off-by: Martin Milata <mmilata> Signed-off-by: Jakub Filak <jfilak> Fixed in upstream git: commit 453531f241d25d34501b2675e0c9d54faa49e783 Author: Martin Milata <mmilata> Date: Mon Aug 12 14:19:28 2013 +0200 Always choose a crash thread If we don't know the crash thread, just choose the first one in order to generate a valid uReport. Closes rhbz#994747. Signed-off-by: Martin Milata <mmilata> Signed-off-by: Jakub Filak <jfilak> commit b9bc44b77aa6922df216565ed2fcd842e9ce5128 Author: Martin Milata <mmilata> Date: Mon Aug 12 14:19:27 2013 +0200 Try harder when looking for crash thread Backported from btparser 6a1db1e193db4136f2b170b911a946c30001fd98: The current algorithm cannot handle backtraces with multiple threads containing the designated crash frame such as [1]. We just pick the first one (from sorted threads) with the risk that our guess might be wrong. Fixes abrt/btparser#3. [1] https://bugzilla.redhat.com/attachment.cgi?id=703269 Related to rhbz#994747. Signed-off-by: Martin Milata <mmilata> Signed-off-by: Jakub Filak <jfilak> satyr-0.7-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/satyr-0.7-1.fc18 satyr-0.7-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/satyr-0.7-1.fc19 Package satyr-0.7-1.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing satyr-0.7-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-15360/satyr-0.7-1.fc19 then log in and leave karma (feedback). *** Bug 1001686 has been marked as a duplicate of this bug. *** satyr-0.7-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. satyr-0.7-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. |