Bug 804309
| Summary: | [abrt] abrt-addon-ccpp-2.0.7-4.fc17: abrt-action-analyze-core:106:extract_info_from_core:IndexError: list index out of range | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mikhail <mikhail.v.gavrilov> | ||||
| 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: | 17 | CC: | abrt-devel-list, awilliam, bruno, dvlasenk, hundred17, inbox+redhat, iprikryl, jfrieben, jmoskovc, jsmith.fedora, kklic, kparal, mads, marcos.brito.carvalho, mikhail.v.gavrilov, mjw, mmilata, mtoman, nb, npajkovs, robatino, salrefrisal | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i686 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | abrt_hash:80e073a19635ff8fdf61be575fcf17733ebbfc30 RejectedBlocker AcceptedNTH | ||||||
| Fixed In Version: | abrt-2.0.10-1.fc17 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-04-18 22:58:16 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: | 752653 | ||||||
| Attachments: |
|
||||||
|
Description
Mikhail
2012-03-17 18:02:38 UTC
Created attachment 570815 [details]
File: backtrace
Create backtrace for tracker process with Local GNU Debugger Package: abrt-addon-ccpp-2.0.7-4.fc17 OS Release: Fedora release 17 (Beefy Miracle) try create backtrace for evolution Package: abrt-addon-ccpp-2.0.7-4.fc17 OS Release: Fedora release 17 (Beefy Miracle) I have tried to create an error repor for gnome-screenshot. Package: abrt-addon-ccpp-2.0.7-4.fc17 OS Release: Fedora release 17 (Beefy Miracle) I think this happened after google-chrome crashed and abrt sprung into action. Package: abrt-addon-ccpp-2.0.7-4.fc17 Architecture: x86_64 OS Release: Fedora release 17 (Beefy Miracle) trying to report a segfault Package: abrt-addon-ccpp-2.0.7-4.fc17 OS Release: Fedora release 17 (Beefy Miracle) This is caused by Bug 805447 - eu-unstrip emits garbage for librt.so.1 It is however a bug in abrt that it doesn't ignore invalid lines. Fixed by: --- abrt-action-analyze-core 2012-03-21 11:13:21.376638423 +0100 +++ /usr/bin/abrt-action-analyze-core 2012-03-21 11:21:20.609658068 +0100 @@ -100,7 +100,7 @@ for line in lines: b_ids_line = line.split() - if len(b_ids_line) > 2: + if len(b_ids_line) > EXECUTABLE: # [exe] -> the executable itself # linux-vdso.so.1 -> Virtual Dynamic Shared Object if b_ids_line[EXECUTABLE] not in ["linux-vdso.so.1"]: (Which also can be used as a workaround.) These bugs will prevent reporting of other more serious bugs and is thus very unfortunate while we are testing. I thus nominate this as a f17betablocker. This is definitely a Final blocker: "All applications listed under the Applications menu or category must withstand a basic functionality test and not crash after a few minutes of normal use. They must also have working Help and Help -> About menu items" https://fedoraproject.org/wiki/Fedora_17_Final_Release_Criteria However, it seems quite logical we should demand to have ABRT functional earlier (Beta or Alpha), because it can catch a lot of bugs in Fedora Branched. I haven't found such criterion though. If other QA guys agree, I would be OK with adding this new criterion to Alpha/Beta and then mark this bug as a Beta blocker. Note that eu-unstrip (and thus abrt) apparently works just fine in many cases, and this issue might thus be less serious than I thought. I'm not sure I'd agree with a criterion to have abrt working at Alpha/Beta stage at least, since it can be fixed with an update. It may be worthwhile at final, not sure... -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers -1 blocker, +1 NTH -1 blocker, +1 NTH I'm -1 blocker here too, mainly on the basis that this isn't stopping all abrt reports, only a few. I've filed several abrt reports over the last few days without any issues. I'm +/-0 NTH, since it's so easy to fix with an update, but I guess we might want to make sure as many live crashes as possible can be reported. That's three -1s, so setting rejectedblocker: NTH status is still open, currently at +2. Kamil or Mads, if you come up with further data that merits re-consideration as blocker, please do add it! -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers -1 blocker +1 NTH - it'd be nice to have abrt working for beta -1 blocker +0 NTH Arguably this will help with testing and people using live images aren't likely to updates. However with it affecting only some aborts and people doing installs likely getting updates, I am not convinced we need this for the beta release. try create backtrace for nautilus Package: abrt-addon-ccpp-2.0.7-4.fc17 OS Release: Fedora release 17 (Beefy Miracle) I was initially afraid this stops most of the crashes being reported. If it concerns only some fraction of them, I'm -1 blocker +1 NTH. Discussed at 2012-03-30 NTH review meeting. Accepted as NTH as this affects reports of installation bugs and can't be fixed with an update for that context. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers (In reply to comment #7) > This is caused by Bug 805447 - eu-unstrip emits garbage for librt.so.1 There is now an upstream fix for this issue in elfutils. Do you want us to backport that to the fedora elfutils package? Or is your workaround in abrt enough for now? (In reply to comment #19) > (In reply to comment #7) > > This is caused by Bug 805447 - eu-unstrip emits garbage for librt.so.1 > > There is now an upstream fix for this issue in elfutils. Do you want us to > backport that to the fedora elfutils package? Or is your workaround in abrt > enough for now? - I'm going to add the patch with the proposed fix to F17, but would be great if this is also fixed in eu-unstrip - F17 is not yet so old to not backport it ;) 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 Package abrt-2.0.10-1.fc17, libreport-2.0.10-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.10-1.fc17 libreport-2.0.10-2.fc17' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-5200/abrt-2.0.10-1.fc17,libreport-2.0.10-2.fc17 then log in and leave karma (feedback). (In reply to comment #20) > - I'm going to add the patch with the proposed fix to F17, but would be great > if this is also fixed in eu-unstrip - F17 is not yet so old to not backport it > ;) elfutils-0.153-2.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/elfutils-0.153-2.fc17 Fix for bug 805447 - eu-unstrip emits garbage for librt.so.1 But it currently seems a bit stuck because of the beta change deadline. Testing and karma appreciated to get it into f17 soon. Beta is out, moving to F17 Final NTH 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. |