Masamichi HOSODA <truer...@sea.plala.or.jp> writes:
> In mingw, lilypond crashes as follows.
> Does someone know this reason?
>
> ```
> C:\tmp\lilypond-2.19.16-0.mingw\$_OUTDIR\usr\bin>type test.ly
> { c d e f g a b }
>
> C:\tmp\lilypond-2.19.16-0.mingw\$_OUTDIR\usr\bin>lilypond test.ly
> GNU LilyPond 2.19.16
> Processing `test.ly'
> Parsing...
> test.ly:1: warning: no \version statement found, please add
>
> \version "2.19.16"
>
> for future compatibility
> Interpreting music...
> Preprocessing graphical objects...terminate called after throwing an instance
> of
> 'std::bad_alloc'
> what(): std::bad_alloc
No idea. Looks like out of memory.
> In freebsd-x86, gs fails as follows.
> (I tested this on 64bit FreeBSD. Perhaps it may succeed on 32bit FreeBSD.)
>
> ```
> $ cat test.ly
> { c d e f g a b }
>
> $ ./lilypond test.ly
> GNU LilyPond 2.19.16
> Processing `test.ly'
> Parsing...
> test.ly:1: warning: no \version statement found, please add
>
> \version "2.19.16"
>
> for future compatibility
> Interpreting music...
> Preprocessing graphical objects...
> Finding the ideal number of pages...
> Fitting music on 1 page...
> Drawing systems...
> Layout output to `test.ps'...
> Converting to `./test.pdf'...
> warning: `(gs -q -dSAFER -dDEVICEWIDTHPOINTS=595.28
> -dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200
> -sDEVICE=pdfwrite -sOutputFile=./test.pdf -c.setpdfwrite -ftest.ps)' failed
> (139)
>
> fatal error: failed files: "test.ly"
That's a SIGSEGV. Not something that a GhostScript executable should be
throwing. Could it be that the 64-bit cross compilation causes
problems?
--
David Kastrup
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
