| Summary: | [abrt] lilypond-2.14.2-1.fc16: scm_gc_mark: Process /usr/bin/lilypond was killed by signal 11 (SIGSEGV) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Christopher Antila <christopher> | ||||||||
| Component: | lilypond | Assignee: | Gwyn Ciesla <gwync> | ||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 16 | CC: | gwync, mitr | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | abrt_hash:07ff2ad6320939cc8ce0d941d72cb39d48989570 | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2013-02-14 01:53:53 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Attachments: |
|
||||||||||
|
Description
Christopher Antila
2012-04-12 05:11:54 UTC
Created attachment 576936 [details]
File: maps
Created attachment 576937 [details]
File: backtrace
A: Is this repeatable? B: Does this occur with other .ly files? C: Can you attach one where it crashes, and if applicable, one where it doesn't? You can also email me directly to my BZ email address if you'd rather not have them publically available. Hi, and thanks for the quick response. A) No. B) No. C) No. I didn't even notice the crash except through ABRT. If you don't mind, I'd like to keep the bug open and I'll experiment with the file and whether I can make it crash LilyPond again. But I won't be able to do that for a month. This is definitely low priority, but if we can find and fix an obscure bug, why not? Never hurts. :) Keep me posted. ?????????? backtrace_rating: 4 Package: lilypond-2.14.2-1.fc16 OS Release: Fedora release 16 (Verne) Created attachment 579250 [details]
File: backtrace
I was never able to reproduce this, though I tried more than once. Especially now that you've brought 2.16.0 into updates-testing, let's close about this unless Miloslav adds something in the next couple of days. With lilypond-2.15.39-1.fc17.x86_64 , I get syntax errors with the current version of my reproducer (which is probably different from the one that originally caused the crash) - so I don't think I can help with reproducing this crash either. This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |