Le 06/12/2021 à 17:02, Johannes Feulner a écrit :
When running lilypond on LY-input broken.ly (s. below), lilypond
crashes with SIGSEGV and a temporary file named like
broken.midi.0123abcd remains.
The desired output would be a correct MIDI file without any note
on/off events.
\version
Hello,
On 06/12/2021 16:02, Johannes Feulner wrote:
When running lilypond on LY-input broken.ly (s. below), lilypond
crashes with SIGSEGV and a temporary file named like
broken.midi.0123abcd remains.
The desired output would be a correct MIDI file without any note
on/off events.
\version
When running lilypond on LY-input broken.ly (s. below), lilypond crashes
with SIGSEGV and a temporary file named like broken.midi.0123abcd remains.
The desired output would be a correct MIDI file without any note on/off
events.
\version "2.22.0"
\score {
\new voice {
Thanks,
http://code.google.com/p/lilypond/issues/detail?id=332
Mats Bengtsson wrote:
The following example causes a SIGSEGV in 2.11.20:
\version "2.11.20"
\new Voice \relative c'{
\override RepeatTie #'head-direction = #LEFT c \repeatT
The following example causes a SIGSEGV in 2.11.20:
\version "2.11.20"
\new Voice \relative c'{
\override RepeatTie #'head-direction = #LEFT
c \repeatTie d e f
}
/Mats
--
=
Mats Bengtsson
Signal Proces
The following example gives a SIGSEGV:
\version "2.11.19"
\relative c' { \makeClusters }
/Mats
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
Mats Bengtsson writes:
> By accident, I happened to run lilypond 2.5.0 (todays CVS) on an old
> example file and to my surprise I got a SIGSEGV.
> The file is the hi-neighbor.ly file linked at the bottom of
> http://lists.gnu.org/archive/html/lilypond-user/2004-10/msg00376.html
T
By accident, I happened to run lilypond 2.5.0 (todays CVS) on an old
example file and to my surprise I got a SIGSEGV.
The file is the hi-neighbor.ly file linked at the bottom of
http://lists.gnu.org/archive/html/lilypond-user/2004-10/msg00376.html
/Mats
When I run lilypond 2.3.11 (cygwin) except when running with -w, -v or
--help (so even with no parameters), I get sigsegv.
Compiler: gcc 3.3.1, Guile: 1.6.4
I will try compiling previous versions to find out where the error came in.
Here is the stack trace of running 'lilypond':
#0
just a synonym for
c2.:16
However, then I noticed that
\time 4/4 \repeat tremolo 12 c8
causes a SIGSEGV. So does c1.:8 or any tremolo that
crosses a bar line, such as
\time 4/4 c2.:8 c2.:8
/Mats
Michael Welsh Duggan wrote:
The unfold-all-repeats.ly example in Tips and Tricks demonstrates the
[EMAIL PROTECTED] writes:
> I just tried some modifications of this example with the latest CVS and
> managed to get a SIGSEGV with the following
>
Works for me. Stack trace?
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.n
[EMAIL PROTECTED] writes:
> Here's the stack trace.
> I have Guile 1.6.4, and gcc version 3.2.2.
thanks, I've added an extra check to CVS; I'm still stumped how it is
possible that I don't see your problem. Are you sure you did make
clean before compiling and cvs up went well?
--
Han-Wen Nienh
Here's the stack trace.
I have Guile 1.6.4, and gcc version 3.2.2.
/Mats
Now processing: `/tmp/lyr.ly'
Parsing...Interpreting music...
Program received signal SIGSEGV, Segmentation fault.
Grob::internal_set_grob_property(scm_unused_struct*, scm_unused_struct*) (
this=0x0, s=0x4
I updated against the CVS again, which updated
simultaneous-music-iterator.cc and got rid of the SIGSEGV.
Yet another bug that was fixed almost before it was reported.
Great!
/Mats
Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
I just tried some modifications of this example with the
I just tried some modifications of this example with the latest CVS and
managed to get a SIGSEGV with the following
upper = \notes\relative c'{c d e f g a b c}
lower = \notes\relative c{c d e f g a b c}
text = \lyrics{ a b c d e f g b c }
\score {
<< % added by me
\context
[EMAIL PROTECTED] writes:
> I got a SIGSEGV when trying Lily 2.1.0 on an old file.
> The following small example gives the same problem.
> Of course, I know that the property doesn't exist anymore
> but Lily shouldn't crash anyway.
Thanks, fixed.
--
Han-Wen Nienhuys
I got a SIGSEGV when trying Lily 2.1.0 on an old file.
The following small example gives the same problem.
Of course, I know that the property doesn't exist anymore
but Lily shouldn't crash anyway.
/Mats
--
=
Mats Bengtsson
17 matches
Mail list logo
