Re: Crash in 2.25.4

Le mardi 30 mai 2023 à 22:40 +0200, Jean Abou Samra a écrit : > Le dimanche 28 mai 2023 à 14:37 +0200, Jean Abou Samra a écrit : > > > > One thing I will try when I can is building in a Kubuntu VM. So far, I used > > a VM with the default Ubuntu variant, with GNOME. That would normally not > >

Re: Crash in 2.25.4

Le dimanche 28 mai 2023 à 14:37 +0200, Jean Abou Samra a écrit : > > One thing I will try when I can is building in a Kubuntu VM. So far, I used a > VM with the default Ubuntu variant, with GNOME. That would normally not > matter, but since the desktop environments are > different, maybe

Re: Crash in 2.25.4

> Le 28 mai 2023 à 05:29, Colin Campbell a écrit : > > Just in case it might help, I uninstalled the font, and reran the test file, > successfully. Logs attached to compare against failed run. These logs sound like I was wrong to blame Pango. Apparently, the introduction of emoji

Re: Crash in 2.25.4

On 2023-05-27 20:36, Colin Campbell wrote: Well, colour me embarrassed! First, I had applied your patches using git cola, and received a confirmation screen saying the patches were applied. Being suspicious, I had a look at the actual files with Kate, and found no patches had actually been

Re: Crash in 2.25.4

On 2023-05-27 16:45, Jean Abou Samra wrote: Le dimanche 28 mai 2023 à 00:38 +0200, Jean Abou Samra a écrit : Le samedi 27 mai 2023 à 16:31 -0600, Colin Campbell a écrit : I generally keep my system current, and libpango is at 1.0-0 already. The "1.0" version number denotes an ABI

Re: Crash in 2.25.4

Le dimanche 28 mai 2023 à 00:38 +0200, Jean Abou Samra a écrit : > Le samedi 27 mai 2023 à 16:31 -0600, Colin Campbell a écrit : > > I generally keep my system current, and libpango is at 1.0-0 already. > The "1.0" version number denotes an ABI compatibility promise as far as I > understand;

Re: Crash in 2.25.4

Le samedi 27 mai 2023 à 16:31 -0600, Colin Campbell a écrit : > I generally keep my system current, and libpango is at 1.0-0 already. The "1.0" version number denotes an ABI compatibility promise as far as I understand; current versions of Pango are actually around 1.50. (1.0.0 is from around

Re: Crash in 2.25.4

On 2023-05-27 16:10, Jean Abou Samra wrote: Le dimanche 28 mai 2023 à 00:05 +0200, Jean Abou Samra a écrit : If Pango fails to correctly substitute values in the FcConfig, it could potentially mean that it's passed with some fields uninitialized to Fontconfig. That could explain why the

Re: Crash in 2.25.4

Le dimanche 28 mai 2023 à 00:05 +0200, Jean Abou Samra a écrit : > If Pango fails to correctly substitute values in the FcConfig, it could > potentially mean that it's passed with some fields uninitialized to > Fontconfig. That could explain why the error is not > reproducible; the value of

Re: Crash in 2.25.4

Le samedi 27 mai 2023 à 07:50 +0200, Jean Abou Samra a écrit : > > With lilypond 2.25.6 and your second patch applied, here are 2 .PDFs: > > first is without the offending font installed, the second is the temporary > > file produced when the font is present. > > > Thanks, but I am more

Re: Crash in 2.25.4

> > With lilypond 2.25.6 and your second patch applied, here are 2 .PDFs: first > is without the offending font installed, the second is the temporary file > produced when the font is present. > Thanks, but I am more interested in the log than the PDF for this one.

Re: Crash in 2.25.4

On 2023-05-26 02:24, Jean Abou Samra wrote: Good that you can reproduce again. Now, can you try the patch with FcPatternPrint and send the log? (No need for FC_DEBUG or --verbose or --ps this time.) With lilypond 2.25.6 and your second patch applied, here are 2 .PDFs: first is without

Re: Crash in 2.25.4

Le jeudi 25 mai 2023 à 19:06 -0600, Colin Campbell a écrit : > I believe we now have a Bingo! > > I d/l and built lilypond 2.25.5 from the website, and ran it against the > test file; it ran successfully. > > I re-installed the fonts-noto-color-emoji package, and ran lilypond > 2.25.5 again,

Re: Crash in 2.25.4

Le mercredi 24 mai 2023 à 20:31 -0600, Colin Campbell a écrit : > Applied this on top of your previous patch; let me know if you want it  > done differently. > > Again, no problems applying, compiling lilypond, nor compiling the test > file. > > Resulting .PDF attached Sorry for not being

Re: Crash in 2.25.4

On 2023-05-23 14:38, Jean Abou Samra wrote: Le mardi 23 mai 2023 à 22:08 +0200, Jean Abou Samra a écrit : So Pango is apparently requesting a font with colored glyphs from Fontconfig... Speaking of which, I would also be interested in the output with ``` diff --git

Re: Crash in 2.25.4

On 2023-05-23 13:28, Jean Abou Samra wrote: Colin: it's really hard to debug this remotely (we might have to resort to VNC or such, I'm afraid...) but there is one simple thing I would be interested in: if you apply this patch, recompile LilyPond and redo the test, what happens? ``` diff

Re: Crash in 2.25.4

Le mercredi 24 mai 2023 à 09:08 +, Werner LEMBERG a écrit : > > So Pango is apparently requesting a font with colored glyphs from > > Fontconfig... > > A bug? Probably. So far, I've been unable to understand where this happens; "git grep FC_COLOR" yields no results in the Pango source

Re: Crash in 2.25.4

> So Pango is apparently requesting a font with colored glyphs from > Fontconfig... A bug? Werner

Re: Crash in 2.25.4

Le mardi 23 mai 2023 à 22:08 +0200, Jean Abou Samra a écrit : > So Pango is apparently requesting a font with colored glyphs from > Fontconfig... Speaking of which, I would also be interested in the output with ``` diff --git a/lily/all-font-metrics.cc b/lily/all-font-metrics.cc index

Re: Crash in 2.25.4

Le mardi 23 mai 2023 à 21:15 +0200, Jean Abou Samra a écrit : > Le lundi 22 mai 2023 à 08:07 +, Werner LEMBERG a écrit : > > > Regarding (2) I'm not sure where exactly the problem lies (i.e., whether it > > is a LilyPond or a Pango issue). > > I'm rather sure it's a Pango or Fontconfig

Re: Crash in 2.25.4

Le mardi 23 mai 2023 à 21:15 +0200, Jean Abou Samra a écrit : > Le lundi 22 mai 2023 à 08:07 +, Werner LEMBERG a écrit : > > > Regarding (2) I'm not sure where exactly the problem lies (i.e., whether it > > is a LilyPond or a Pango issue). > > I'm rather sure it's a Pango or Fontconfig

Re: Crash in 2.25.4

Le lundi 22 mai 2023 à 08:07 +, Werner LEMBERG a écrit : > Regarding (2) I'm not sure where exactly the problem lies (i.e., whether it > is a LilyPond or a Pango issue). I'm rather sure it's a Pango or Fontconfig issue. Based on the fact that we use Pango's FreeType backend, which is not

Re: Crash in 2.25.4 Solved

> Following your suggestion, Werner, I tried the test file with the > cairo back end, and it worked as expected. Great, please send me the created PDF for further analysis – just to be sure :-) > I then deleted the Noto Color Emoji font (synaptic also deleted > texlive fonts extra links), and

Re: Crash in 2.25.4 Solved

On 2023-05-22 02:07, Werner LEMBERG wrote: (1) You have the font 'Noto Color Emoji' installed on your system (the new one, with scalable glyphs using the 'COLR' v1 format). Say `fc-list | less` to find out where it is located. This font format is not supported by GhostScript

Re: Crash in 2.25.4

Colin, >> All this comes about as I'm thinking of getting back to >> some documentation work, and wanted to compile docs locally. I'll >> still keep that goal in mind. >> >> If you can still reproduce the problem after this cleaning, could >> you run >> >> ``` >> FC_DEBUG=2025

Re: Crash in 2.25.4

(Adding back the bug list) Le samedi 20 mai 2023 à 17:51 -0600, Colin Campbell a écrit : > > I redid git bisect today, doing everything on the command line (I used > Frescobaldi last night). Each time, I ran " > > ``` >  colin@Calvin:/Work/lilypond/lilypond$ cd build >

Re: Crash in 2.25.4

Le vendredi 19 mai 2023 à 23:00 -0600, Colin Campbell a écrit : > The result of git bisect: > > 1db87a2537d6d5ef6631cfbda63954c0a6ee095 is the first bad commit > commit d1db87a2537d6d5ef6631cfbda63954c0a6ee095 > Author: Jonas Hahnfeld > Date:   Mon Apr 3 22:57:26 2023 +0200 > > Doc: Avoid

Re: Crash in 2.25.4

The result of git bisect: 1db87a2537d6d5ef6631cfbda63954c0a6ee095 is the first bad commit commit d1db87a2537d6d5ef6631cfbda63954c0a6ee095 Author: Jonas Hahnfeld Date:   Mon Apr 3 22:57:26 2023 +0200    Doc: Avoid full stop in node names    This propagates the changes from commit c245707e4f to

Re: Crash in 2.25.4

On 2023-05-19 15:43, Jean Abou Samra wrote: Le vendredi 19 mai 2023 à 21:00 +0200, Jean Abou Samra a écrit : Can you try to find which commit introduced the problem for you, using 'git bisect'? Alternatively: what's your Ubuntu version? I just installed a fresh Ubuntu 23.04 VM and compiled

Re: Crash in 2.25.4

Le vendredi 19 mai 2023 à 21:00 +0200, Jean Abou Samra a écrit : > Can you try to find which commit introduced the problem for you, using 'git > bisect'? Alternatively: what's your Ubuntu version? I just installed a fresh Ubuntu 23.04 VM and compiled LilyPond in it but I cannot reproduce the

Re: Crash in 2.25.4

Le vendredi 19 mai 2023 à 12:26 -0600, Colin Campbell a écrit : > > On 2023-05-19 11:03, Jean Abou Samra wrote: > > \version "2.25.5" > > > > #(define-markup-command (db layout props arg) (markup?) > >     (let ((stil (interpret-markup layout props arg))) > >   (pretty-print (ly:stencil-expr

Re: Crash in 2.25.4

On 2023-05-19 11:03, Jean Abou Samra wrote: \version "2.25.5" #(define-markup-command (db layout props arg) (markup?) (let ((stil (interpret-markup layout props arg))) (pretty-print (ly:stencil-expr stil)) stil)) \markup \db abc Terminal output: ###

Re: Crash in 2.25.4

Le vendredi 19 mai 2023 à 09:43 -0600, Colin Campbell a écrit : > > Of all the errors you posted, which one is it now? > ``` > colin@Calvin:/Work$ lilypond Non-Musical.ly   > GNU LilyPond 2.25.5 (running Guile 2.2) > Processing `Non-Musical.ly' > Parsing... > Interpreting music...

Re: Crash in 2.25.4

On 2023-05-18 23:30, Jean Abou Samra wrote Thanks, Werner, for the suggestion. I just tried it, and lilypond still errors as before. Of all the errors you posted, which one is it now? colin@Calvin:/Work$ lilypond Non-Musical.ly GNU LilyPond 2.25.5 (running Guile 2.2) Processing

Re: Crash in 2.25.4

> Thanks, Werner, for the suggestion. I just tried it, and lilypond still > errors as before. Of all the errors you posted, which one is it now?

Re: Crash in 2.25.4

On 2023-05-18 22:09, Werner LEMBERG wrote: ran make successfully, got carried away and may have shot myself in the foot by running sudo make install. You should actually do ``` make bytecode sudo make install-bytecode ``` Without installing the Guile bytecode, LilyPond is slooow. Thanks,

Re: Crash in 2.25.4

> ran make successfully, got carried away and may have shot myself in > the foot by running sudo make install. You should actually do ``` make bytecode sudo make install-bytecode ``` Without installing the Guile bytecode, LilyPond is slooow. Werner

Re: Crash in 2.25.4

On 2023-05-18 21:07, Colin Campbell wrote: On 2023-05-18 01:55, Jean Abou Samra wrote: I'm going nuclear tomorrow: delete my clone, and start over. No need to be *that* nuclear, you can just remove the build directory and start a fresh build. Deleted /build,  mkdir build, cd build

Re: Crash in 2.25.4

On 2023-05-18 01:55, Jean Abou Samra wrote: I'm going nuclear tomorrow: delete my clone, and start over. No need to be *that* nuclear, you can just remove the build directory and start a fresh build. Deleted /build,  mkdir build, cd build ran make successfully, got carried away and

Re: Crash in 2.25.4

Wonderful, thank you! \-- Gwyn Ciesla she/her/hers \ in your fear, seek only peace in your fear, seek only love \-d. bowie Sent from Proton Mail mobile \ Original Message On May 18, 2023, 12:53 PM, Jean Abou

Re: Crash in 2.25.4

Le jeudi 18 mai 2023 à 11:27 +0200, Jean Abou Samra a écrit : > Gwyn, is it convenient for you to test patches? I think I see what this is > caused by, but I cannot reproduce the bug in a local build (knowing what > exact compiler flags are used in Fedora's builds > might help). > I'd like to

Re: Crash in 2.25.4

Gwyn, is it convenient for you to test patches? I think I see what this is caused by, but I cannot reproduce the bug in a local build (knowing what exact compiler flags are used in Fedora's builds might help). I'd like to know if this fixes it: ``` diff --git a/lily/all-font-metrics-scheme.cc

Re: Crash in 2.25.4

> I'm going nuclear tomorrow: delete my clone, and start over. No need to be *that* nuclear, you can just remove the build directory and start a fresh build.

Re: Crash in 2.25.4

> Le 18 mai 2023 à 05:49, Colin Campbell a écrit : > > Attached console output. I'll do a git pull and recompile a bit later, and > report what happens. Note that the same test file when compiled using > Frescobaldi as a front end, produces the following output: > > > Starting lilypond

Re: Crash in 2.25.4

On 2023-05-17 18:25, Jean Abou Samra wrote: Could you please run with `lilypond --verbose` and send the output? Thanks, Jean Now lilypond blows up in make: colin@Calvin:/Work/lilypond/lilypond/build$ make -j3 SILENT=1 PythonUI_Init() PythonUI_Init() PythonUI_Init()

Re: Crash in 2.25.4

Attached console output. I'll do a git pull and recompile a bit later, and report what happens. Note that the same test file when compiled using Frescobaldi as a front end, produces the following output: Starting lilypond 2.25.5 [Non-Musical.ly]... programming error: unknown context mod tag

Re: Crash in 2.25.4

Le mercredi 17 mai 2023 à 17:48 -0600, Colin Campbell a écrit : > Happens to me on Ubuntu as well: I don't think that's the same bug. Regarding this: > Fontconfig error: No writable cache directories This error popped up at some point during the current cycle before being fixed shortly

Re: Crash in 2.25.4

Happens to me on Ubuntu as well: && colin@Calvin:/Work$ lilypond Non-Musical.ly GNU LilyPond 2.25.5 (running Guile 2.2) Fontconfig error: No writable cache directories Processing `Non-Musical.ly' Parsing... Interpreting music... Preprocessing graphical objects...

Re: Crash in 2.25.4

Le mercredi 17 mai 2023 à 20:02 +, Gwyn Ciesla via bug-lilypond a écrit : > Attaching reproducer. > > From Fedora bug: > > When I attempt to build a score using a PianoStaff or GrandStaff (which > contains more than one sub-staff), lilypond crashes. > > Reproducible: Always > > Steps to

Re: Crash with bare duration at the start of a Voice-alias context

Le 14/04/2022 à 09:38, Simon Albrecht a écrit : Hello list, this causes a crash while Interpreting music (Exiting with return code 11.): % also happens with 2.20.0 \version "2.23.6" %%{ % also happens with VaticanaVoice,MedicaeaVoice,PetrucciVoice \new

Re: Crash from embedded comment

Il giorno gio, nov 19 2020 at 16:58:31 -0500, Trevor Bača ha scritto: (minimum-distance . 12) % errant comment causes crash You should use `;` to add a comment in a Scheme block, so it doesn't look like a bug to me. v2.20 did not produce an error, but the documentation already

Re: Crash with simultaneous-duplicating music function and \once\offset

Simon Albrecht writes: > On 18.07.2018 10:59, David Kastrup wrote: >> basically one of the calls to \offset gets junked because of LilyPond >> not being able to disentangle them (one could extend the code to handle >> this case but it would still balk at more complex combinations). > > Great!

Re: Crash with simultaneous-duplicating music function and \once\offset

On 18.07.2018 10:59, David Kastrup wrote: basically one of the calls to \offset gets junked because of LilyPond not being able to disentangle them (one could extend the code to handle this case but it would still balk at more complex combinations). Great! This is exactly what would be needed

Re: Crash with simultaneous-duplicating music function and \once\offset

Simon Albrecht writes: > Hello everybody, > > this combination of a custom music function that combines the music > simultaneously with itself and a \once\offset command causes LilyPond > to crash (exit with return code 11): > > > \version "2.19.82" > test = >

Re: Crash with simultaneous-duplicating music function and \once\offset

On 17.07.2018 20:46, David Kastrup wrote: I got Tracker issue: 5386 (https://sourceforge.net/p/testlilyissues/issues/5386/) Rietveld issue: 367760043 (https://codereview.appspot.com/367760043) Issue description: Make grob-transform robust against cloned invocations Well, "robust" is a bit

Re: Crash with simultaneous-duplicating music function and \once\offset

Aaron Hill writes: > On 2018-07-17 11:46, David Kastrup wrote: >> Aaron Hill writes: >>> I tried manually duplicating the music: >>> >>> >>> \version "2.19.82" >>> music = { \once \offset length 5 Stem c'4 c'4 } >>> musicCopy = { \once \offset length 5 Stem c'4 c'4 } >>> \new Staff

Re: Crash with simultaneous-duplicating music function and \once\offset

On 2018-07-17 11:46, David Kastrup wrote: Aaron Hill writes: I tried manually duplicating the music: \version "2.19.82" music = { \once \offset length 5 Stem c'4 c'4 } musicCopy = { \once \offset length 5 Stem c'4 c'4 } \new Staff { c'4 << \music \musicCopy >> c'4 } This

Re: Crash with simultaneous-duplicating music function and \once\offset

Aaron Hill writes: > On 2018-07-15 20:09, Aaron Hill wrote: >> Seems the custom music function is not needed to reproduce a crash. >> >> >> \version "2.19.82" >> music = { \once \offset length 5 Stem 4 4 } >> << \music \music >> >> >> >> This also results in: >> >>> GNU LilyPond

Re: Crash with simultaneous-duplicating music function and \once\offset

David Kastrup writes: >> David mentioned two issues: using `<<...>>` top-level and using >> unpitched notes. >> >> Consider the following not-quite-as-minimal example: >> >> >> \version "2.19.82" >> music = { \once \offset length 5 Stem c'4 c'4 } >> \new Staff { c'4 << \music \music

Re: Crash with simultaneous-duplicating music function and \once\offset

Aaron Hill writes: > On 2018-07-15 20:09, Aaron Hill wrote: >> Seems the custom music function is not needed to reproduce a crash. >> >> >> \version "2.19.82" >> music = { \once \offset length 5 Stem 4 4 } >> << \music \music >> >> >> >> This also results in: >> >>> GNU LilyPond

Re: Crash with simultaneous-duplicating music function and \once\offset

On 2018-07-15 20:09, Aaron Hill wrote: Seems the custom music function is not needed to reproduce a crash. \version "2.19.82" music = { \once \offset length 5 Stem 4 4 } << \music \music >> This also results in: GNU LilyPond 2.19.82 Processing `crash.ly' Parsing...

Re: Crash with simultaneous-duplicating music function and onceoffset

Hello, On Sun, 15 Jul 2018 20:09:52 -0700, Aaron Hill wrote: > On 2018-07-15 18:21, Simon Albrecht wrote: > > Hello everybody, > > > > this combination of a custom music function that combines the music > > simultaneously with itself and a \once\offset command causes LilyPond > > to crash

Re: Crash with simultaneous-duplicating music function and \once\offset

On 2018-07-15 18:21, Simon Albrecht wrote: Hello everybody, this combination of a custom music function that combines the music simultaneously with itself and a \once\offset command causes LilyPond to crash (exit with return code 11): \version "2.19.82" test =

Re: crash during musicxml2ly

Hello Frederic, On Sat, 14 Apr 2018 09:42:20 +, Frédéric Gohier wrote: > hello, > > I face a crash when run the command line : > /usr/local/bin/musicxml2ly --nd --nrp --npl --no-beaming -m > MusicXMLV2_from_sibelius7.xml > > the traceback is : > Traceback (most

Re: crash during musicxml2ly

Please see http://lilypond.org/doc/v2.19/Documentation/contributor/patches -- Phil Holmes "Frédéric Gohier" wrote in message news:he1pr1001mb140284687c61080bd2d06ee9ba...@he1pr1001mb1402.eurprd10.prod.outlook.com... hello, I face a crash when run the command line :

Re: Crash: "programming error: trying to freeze time"

Thanks for catching the issues with my example. I've tried to strip it down even farther to the absolute simplest example that causes this crash. Try this: \version "2.19.49" << % To get an interesting alternative bug, comment out the next line. Lilypond finishes, but only engraves the first

Re: Crash: "programming error: trying to freeze time"

Hello McLaren, in order to demonstrate good will, please apply the suggestions on code formatting and minimal examples I gave on the parallel post here as well; then I’ll act on the report. Best, Simon On 13.11.2016 07:14, mclaren wrote: also "programming error: trying to move backward in

Re: Crash: Unterminated tie with articulation in temporary voice

Am 09.09.2016 um 09:24 schrieb Mark Knoop: > At 01:57 on 09 Sep 2016, Thomas Morley wrote: >> 2016-09-09 0:13 GMT+02:00 Simon Albrecht : >> _Cannot_ confirm crash with a build from most recent master, i.e from: >> commit 5944d20489bb5b8e4c4907fa3b3bcae9ec275ccb >> >>

Re: Crash: Unterminated tie with articulation in temporary voice

At 01:57 on 09 Sep 2016, Thomas Morley wrote: >2016-09-09 0:13 GMT+02:00 Simon Albrecht : >_Cannot_ confirm crash with a build from most recent master, i.e from: >commit 5944d20489bb5b8e4c4907fa3b3bcae9ec275ccb > >with: >gcc --version >gcc (Ubuntu 5.4.0-6ubuntu1~16.04.2)

Re: Crash: Unterminated tie with articulation in temporary voice

Simon Albrecht writes: > On 08.09.2016 21:53, David Kastrup wrote: >> Urs Liska writes: >> >>> The attached file produces a crash on LilyPond 2.19.47 while it compiles >>> fine on 2.18.2. I don't have any earlier 2.19 versions ready to narrow >>> it

Re: Crash: Unterminated tie with articulation in temporary voice

On 08.09.2016 21:53, David Kastrup wrote: Urs Liska writes: The attached file produces a crash on LilyPond 2.19.47 while it compiles fine on 2.18.2. I don't have any earlier 2.19 versions ready to narrow it down further. What does "produces a crash" mean? What is the

Re: Crash: Unterminated tie with articulation in temporary voice

Urs Liska writes: > The attached file produces a crash on LilyPond 2.19.47 while it compiles > fine on 2.18.2. I don't have any earlier 2.19 versions ready to narrow > it down further. What does "produces a crash" mean? What is the output? What is the error message? In

Re: Crash with Completion_heads_engraver and a bare duration

On 05.02.2016 00:00, Simon Albrecht wrote: the following code crashes: % \version "2.19.36" \layout { \context { \Voice \remove "Note_heads_engraver" \consists "Completion_heads_engraver" } } { \breve } % Removing Note_heads_engraver is not essential to

Re: Crash with tupletFullLength = ##t

Hello Mark, this would have been in the domain of the bug list. On 23.12.2015 19:58, Mark Knoop wrote: When tupletFullLength is set to ##t, the TupletBracket is actually *shortened* by a following RehearsalMark. This doesn't happen with tupletFullLength = ##f. This is merely ugly when a

Re: crash with gs-error

On 2015-07-11 03:06 PM, Thomas Morley wrote: The following crashes with released 2.19.22 %% snippet-start \version 2.19.22 \paper { first-page-number = #-1 } \markuplist \table-of-contents \tocItem Adagio { c''1 } %% snippet-end returning: GNU LilyPond 2.19.22 Processing `table-poking.ly'

Re: crash with gs-error

At least on Ubuntu 15,04, it's the page number -1 that does it. Zero or positive numbers work. Andrew On 12 July 2015 at 07:06, Thomas Morley thomasmorle...@gmail.com wrote: The following crashes with released 2.19.22 %% snippet-start \version 2.19.22 \paper { first-page-number = #-1 }

Re: Crash with make-dynamic-script

Hi, 2014-08-31 14:37 GMT+02:00 Simon Albrecht simon.albre...@mail.de: Hello, yesterday I tried out make-dynamic-script and in my first attempt forgot some : pDolce = #(make-dynamic-script (markup #:dynamic p #:italic dolce)) [...] FWIW, i think you may find this snippet more user-friendly

Re: Crash with make-dynamic-script

Simon Albrecht simon.albre...@mail.de writes: Hello, yesterday I tried out make-dynamic-script and in my first attempt forgot some : pDolce = #(make-dynamic-script (markup #:dynamic p #:italic dolce)) Compiling the attached example file results in fatal error: make-dynamic-markup: Invalid

Re: Crash with make-dynamic-script

Am 31.08.2014 um 14:42 schrieb David Kastrup: Simon Albrecht simon.albre...@mail.de writes: Hello, yesterday I tried out make-dynamic-script and in my first attempt forgot some : pDolce = #(make-dynamic-script (markup #:dynamic p #:italic dolce)) Compiling the attached example file results

Re: Crash with make-dynamic-script

Simon Albrecht simon.albre...@mail.de writes: Am 31.08.2014 um 14:42 schrieb David Kastrup: Simon Albrecht simon.albre...@mail.de writes: Hello, yesterday I tried out make-dynamic-script and in my first attempt forgot some : pDolce = #(make-dynamic-script (markup #:dynamic p #:italic

Re: Crash with \repeat ... \alternative and \remove Bar_engraver on 2.17.26

Cc and Reply-To to bug-lilypond Jim Long lilyp...@umpquanet.com writes: I was researching a method for defining form (repeats, rehearsal marks, etc.) and line breaking in separate, hidden parallel staff contexts, and ran across the following crash: GNU LilyPond 2.17.26 Processing

Re: Crash with \repeat ... \alternative and \remove Bar_engraver on 2.17.26

On Sun, Nov 17, 2013 at 12:15:45AM +0100, David Kastrup wrote: What is this good for? I'm debugging on this URL:http://code.google.com/p/lilypond/issues/detail?id=3663 and though I've gotten the crash under control, my results are not identical to the 2.16 results. I have a hard time

Re: crash report for OSX

FWIW the macports version runs on my machine. I'll use that for now-- i can live with command-line compiling. Be nice to get the GUI-based lilypond.app running, tho. -- View this message in context: http://lilypond.1069038.n5.nabble.com/crash-report-for-OSX-tp151959p152320.html Sent from

Re: crash report for OSX

More info. Ran gdb and at the point I tried to typeset file, got:; 2013-10-13 20:59:34.580 LilyPond[86224:a0f] *** NSTimer ignoring exception 'type 'exceptions.OSError': [Errno 4] Interrupted system call' that raised during firing of timer with target 0x4956d0 and selector 'timerCallback:'

Re: crash with tuplets containing only skips and dynamics

2013/10/12 René Brandenburger r...@brandenburger.lu: Hi, the following snippets crashes lilypond 2.17.26 on windows7 64bit, \version 2.17.26 \times 2/3 {s8\ s8\ s8\!} output: Starte lilypond.exe 2.17.26 [Ohne Titel] ... Processing

Re: crash with tuplets containing only skips and dynamics

René Brandenburger r...@brandenburger.lu writes: Hi, the following snippets crashes lilypond 2.17.26 on windows7 64bit, \version 2.17.26 \times 2/3 {s8\ s8\ s8\!} URL:http://code.google.com/p/lilypond/issues/detail?id=3551 Fixed in 2.17.27. Keith was faster than you. -- David Kastrup

Re: crash with tuplets containing only skips and dynamics

Am 12.10.2013 20:55, schrieb David Kastrup: René Brandenburger r...@brandenburger.lu writes: Hi, the following snippets crashes lilypond 2.17.26 on windows7 64bit, \version 2.17.26 \times 2/3 {s8\ s8\ s8\!} URL:http://code.google.com/p/lilypond/issues/detail?id=3551 Fixed in 2.17.27.

Re: crash report for OSX

SOrry for the delay - I didn't get the direct email you sent. Anyway, I was using the initial sample file that Lilypond generates at first run. I've tried Lilypond versions 16,15 and 14, with same failure. There's something fundamentally wrong with the Lilypond compiled OSX version. --

Re: crash report for OSX

Carl Witthoft c...@witthoft.com wrote in message news:1381601075054-152192.p...@n5.nabble.com... SOrry for the delay - I didn't get the direct email you sent. Anyway, I was using the initial sample file that Lilypond generates at first run. I've tried Lilypond versions 16,15 and 14, with same

Re: crash report for OSX

On 13-10-12 02:42 PM, Phil Holmes wrote: Carl Witthoft c...@witthoft.com wrote in message news:1381601075054-152192.p...@n5.nabble.com... SOrry for the delay - I didn't get the direct email you sent. Anyway, I was using the initial sample file that Lilypond generates at first run. I've

Re: crash report for OSX

Hi -- OSX 10.6.8, iMac core Duo Intel LilyPond compiled binary off the main site, 2.16.2. All the previous versions I tried (back thru 2.14) were from the repository at lilypond.org as well. More tests: I invoked the executable `Lilypond/Contents/Resources/bin/lilypond` directly from the command

Re: crash report for OSX

Forwarding to OP... 2013/10/8 David Kastrup d...@gnu.org Carl Witthoft c...@witthoft.com writes: For christsake lose that idiotic Top post filter will you? Latest stable LilyPond, trying to compile the example file. OSX 10.6.8 on iMac IntelCore2Duo. Which example file? -- David

Re: crash report for OSX

On Tue, Oct 8, 2013 at 1:12 AM, Carl Witthoft c...@witthoft.com wrote: For christsake lose that idiotic Top post filter will you? Why? Top-posting is the most annoying thing on the Internet. -- Vik ___ bug-lilypond mailing list

Re: crash report for OSX

Carl Witthoft c...@witthoft.com writes: For christsake lose that idiotic Top post filter will you? Latest stable LilyPond, trying to compile the example file. OSX 10.6.8 on iMac IntelCore2Duo. Which example file? -- David Kastrup ___

Re: crash with \partcombine \repeat tremolo when voices cross

On Fri, May 17, 2013 at 4:41 AM, Eluze elu...@gmail.com wrote: reported in the French community http://lilypond-french-users.1298960.n2.nabble.com/Probleme-avec-repeat-tremolo-en-partcombine-tp7579661.html I couldn't find this in the many issues about \partcombine you can circumvent this

Re: crash of musicxml2ly

Hello, 2013/4/24 Laura Conrad lcon...@laymusic.org I attempted to run musicxml2ly on the file http://www2.cpdl.org/wiki/images/9/91/Alessandro_Striggio-Nasce_la_pena-XML.zip using the command musicxml2ly -z --nd --nrp --npl --no-beaming *.zip and musicxml2ly 2.16.1 crashes with the

Re: crash of musicxml2ly

Hello Patrick, 2013/4/24 pls p.l.schm...@gmx.de Laura, you are right. For the time being you will have to unzip the file manually and run musicxml2ly on the .xml file. The conversion with musicxml2ly will be successful (no error messages) but unfortunately the compilation with LilyPond

Re: crash of musicxml2ly

Laura, you are right. For the time being you will have to unzip the file manually and run musicxml2ly on the .xml file. The conversion with musicxml2ly will be successful (no error messages) but unfortunately the compilation with LilyPond (v2.17.15) will fail due to a segmentation fault.

Re: crash when \setting a grob if it is used afterwards

On Thu, Dec 13, 2012 at 09:46:30AM +0100, David Kastrup wrote: Eluze elu...@gmail.com writes: David Kastrup wrote Eluze lt; eluzew@ gt; writes: David Kastrup wrote For an explanation, see lt;URL:http://code.google.com/p/lilypond/issues/detail?id=2870#c7gt; well, here

Re: crash when \setting a grob if it is used afterwards

David Kastrup wrote Eluze lt; eluzew@ gt; writes: David Kastrup wrote For an explanation, see lt;URL:http://code.google.com/p/lilypond/issues/detail?id=2870#c7gt; well, here she only says: GNU LilyPond 2.17.8 Processing `test.ly' Parsing... Interpreting music... You have to try

  1   2   >