Comment #10 on issue 2030 by gra...@percival-music.ca: 2.14.2, dynamic cast
crash introduced in commit 6f6369c0
http://code.google.com/p/lilypond/issues/detail?id=2030
Yes, anything is "reasonable and simple" when it's somebody else doing the
work.
I am not certain that GUB can still buil
Comment #9 on issue 2030 by d...@gnu.org: 2.14.2, dynamic cast crash
introduced in commit 6f6369c0
http://code.google.com/p/lilypond/issues/detail?id=2030
If we chose to do 2.14.3, the fix for Issue 1997 would likely have to go in
as well, or we would be hearing from it...
__
Comment #8 on issue 2030 by plros...@gmail.com: 2.14.2, dynamic cast crash
introduced in commit 6f6369c0
http://code.google.com/p/lilypond/issues/detail?id=2030
The trunk (2.15.x) was fixed long ago. The problem only exists in 2.14.x
and the fix would be to apply my patch to the stable-2.1
Updates:
Status: Verified
Comment #7 on issue 2030 by colingh...@gmail.com: 2.14.2, dynamic cast
crash introduced in commit 6f6369c0
http://code.google.com/p/lilypond/issues/detail?id=2030
To verify this I used the sample code submitted by plroskin in Comment #2
\version "2.14.2"
\sc
Comment #6 on issue 2030 by plros...@gmail.com: 2.14.2, dynamic cast crash
introduced in commit 6f6369c0
http://code.google.com/p/lilypond/issues/detail?id=2030
This ticket is misnamed. The crash is not in dynamic_cast. It was in
dynamic_cast because I miscompiled lilypond. Once I starte
Updates:
Status: Fixed
Labels: fixed_2_15_9 backport
Comment #5 on issue 2030 by k-ohara5...@oco.net: 2.14.2, dynamic cast crash
introduced in commit 6f6369c0
http://code.google.com/p/lilypond/issues/detail?id=2030
Let's point this to issue 1800, then, and mark the fixed versi
Comment #4 on issue 2030 by plros...@gmail.com: 2.14.2, dynamic cast crash
introduced in commit 6f6369c0
http://code.google.com/p/lilypond/issues/detail?id=2030
The fix is to backport 9ff88d12 from master. The patch is attached.
Considering that it's a crash in the latest stable release,
Comment #3 on issue 2030 by gra...@percival-music.ca: 2.14.2, dynamic cast
crash introduced in commit 6f6369c0
http://code.google.com/p/lilypond/issues/detail?id=2030
hmm, interesting. BTW, "make clean" is not reliable either. In my mind,
the only reliable thing is:
- completely remove th
Comment #2 on issue 2030 by plros...@gmail.com: 2.14.2, dynamic cast crash
introduced in commit 6f6369c0
http://code.google.com/p/lilypond/issues/detail?id=2030
The bug as it's entered is bogus. It turns out lilypond has an issue with
the build system. The incremental make is not reliable
Comment #1 on issue 2030 by plros...@gmail.com: 2.14.2, dynamic cast crash
introduced in commit 6f6369c0
http://code.google.com/p/lilypond/issues/detail?id=2030
I can reproduce the issue on a Fedora 16 system, but not on a Fedora 15
system. On the later, I get:
GNU LilyPond 2.14.2
Proces
Status: Accepted
Owner:
Labels: Type-Crash
New issue 2030 by pkx1...@gmail.com: 2.14.2, dynamic cast crash introduced
in commit 6f6369c0
http://code.google.com/p/lilypond/issues/detail?id=2030
Hello!
Lilypond 2.14.2 and the current revision from stable/2.14 crash on this
file:
\version
11 matches
Mail list logo
