Bug 690920
Summary: | [abrt] gtkwave-3.3.15-1.fc14: inflate: Process /usr/bin/gtkwave was killed by signal 11 (SIGSEGV) | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jeff <1nomdeplume> | ||||
Component: | gtkwave | Assignee: | Paul Howarth <paul> | ||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 14 | CC: | paul | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i686 | ||||||
OS: | Unspecified | ||||||
Whiteboard: | abrt_hash:b4fa3e4b431528579a22e787ae019d1569794486 | ||||||
Fixed In Version: | gtkwave-3.3.20-2.fc14 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2011-04-07 11:01:12 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: | |||||||
Attachments: |
|
Description
Jeff
2011-03-25 19:49:31 UTC
Created attachment 487665 [details]
File: backtrace
gtkwave-3.3.20-2.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/gtkwave-3.3.20-2.fc14 gtkwave-3.3.20-2.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/gtkwave-3.3.20-2.fc13 gtkwave-3.3.20-2.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/gtkwave-3.3.20-2.fc15 Is this crash repeatable? Can you please try the updated version from Comment #2, which contains a tentative fix from the program's author. (In reply to comment #5) > Is this crash repeatable? Can you please try the updated version from Comment > #2, which contains a tentative fix from the program's author. I installed the update from updates-testing. I tried to reproduce the bug using the same simulation as before and it works fine. I may have changed the .sav file though since some of the signal names changed. Thanks for your work on this, it is a great program. Was/is the crash repeatable with the old version? You could try it using "yum downgrade gtkwave". gtkwave-3.3.20-2.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report. (In reply to comment #7) > Was/is the crash repeatable with the old version? You could try it using "yum > downgrade gtkwave". I am not able to reproduce the crash with either version, but I hadn't slept for a few days at the time of the crash and it may have been intermittent. gtkwave-3.3.20-2.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report. gtkwave-3.3.20-2.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report. gtkwave-3.3.21-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/gtkwave-3.3.21-1.fc14 gtkwave-3.3.21-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/gtkwave-3.3.21-1.el6 gtkwave-3.3.21-1.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/gtkwave-3.3.21-1.fc13 gtkwave-3.3.21-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/gtkwave-3.3.21-1.fc15 gtkwave-3.3.21-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report. gtkwave-3.3.21-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report. gtkwave-3.3.21-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report. gtkwave-3.3.21-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report. |