Bug 672023
| Summary: | Abrt allows submitting backtraces without *any* debugsymbols | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Christoph Wickert <christoph.wickert> |
| Component: | libreport | Assignee: | Denys Vlasenko <dvlasenk> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | anton, awilliam, dvlasenk, iprikryl, jmoskovc, kklic, mlichvar, mmilata, mtoman, npajkovs, stephent98 |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | AcceptedNTH RejectedBlocker | ||
| Fixed In Version: | libreport-2.0.5.980-1.fc16 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-09-26 01:41:34 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 713565 | ||
|
Description
Christoph Wickert
2011-01-23 09:56:55 UTC
Fixed in upstream git, both master and 1.1.x branch. There were two bugs: 1) ABRT failed to parse the backtrace (because it was produced by the new GDB) The result is that the backtrace was not rated. 2) ABRT allowed to submit the backtrace without rating. Now if the backtrace parser fails, the backtrace is rated as lowest quality. The parser was extended to parse the thread headers produced by the new GDB. Even with this change, the backtrace mentioned in this bug is still rated as lowest quality. (In reply to comment #1) > Fixed in upstream git, both master and 1.1.x branch. If it was fixed in 1.1.x on January 31st, should the fix be in abrt-1.1.17-1.fc15 built on February 6th? I still get empty backtraces on the F15 alpha livemedia. Hi there, any news? Ping?! There is a new version abrt-2.0.0 in updatest-testing which should have this fixed. I just submitted a report with no symbols: Bug 698468 - [abrt] gnome-shell-2.91.92-3.fc15: Process /usr/bin/gnome-shell was killed by signal 6 (SIGABRT) abrt-2.0.1-1.fc15.x86_64 Steve, thank you for the pointer. Btparser rates the backtrace it with 0. Function check_backtrace_and_allow_send in src/gui-wizard-gtk/wizard.c incorrectly expects the rating to have a value between 1 and 4; 0 is being ignored. Fixed in commit 884c0aed054302cb1cbb71c2b21c12df92a7e6e4 in upstream git. abrt-2.0.1-2.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/abrt-2.0.1-2.fc15 Package abrt-2.0.1-2.fc15: * should fix your issue, * was pushed to the Fedora 15 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.1-2.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/abrt-2.0.1-2.fc15 then log in and leave karma (feedback). (In reply to comment #8) > Fixed in commit 884c0aed054302cb1cbb71c2b21c12df92a7e6e4 in upstream git. Thanks, Karel. https://fedorahosted.org/abrt/changeset/884c0aed054302cb1cbb71c2b21c12df92a7e6e4 I couldn't figure out a way to recreate a backtrace with a zero rating, but could test the fix by editing the rating file: -1, 0, 5 were all identified as unusable by abrt-gui. abrt-2.0.1-2.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report. Reopening, because it is back in 2.0.5 as you can see in bug 740218. Will roll a new update with a fix for this today or tmrw - proposing as a beta blocker, since this can create a lot of noise in bz. Discussed at the 2011-09-21 go/no-go meeting (note: in #fedora-meeting-1), acting as a blocker review meeting. Agreed that this is not a release blocker, as it doesn't prevent the submission of good reports, but nice to have, as it will prevent us getting useless reports from the live image. Fixed in git (commit: 0dba21e4e82ec222d895750565e513151b675c27) libreport-2.0.5.980-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/libreport-2.0.5.980-1.fc16 Package libreport-2.0.5.980-1.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing libreport-2.0.5.980-1.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/libreport-2.0.5.980-1.fc16 then log in and leave karma (feedback). libreport-2.0.5.980-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. |