Re: Segmentation fault with a bad systemStartDelimiter

On 13.07.2016 22:54, Nathan Ho wrote: Hi list, A bad value for StaffGroup.systemStartDelimiter appears to cause a segmentation fault: I can confirm that. \version "2.19.45" \new StaffGroup \with { systemStartDelimiter = #'aaa } { c'4 } $ lilypond test.ly GNU LilyPond 2.19.45

Segmentation fault with a bad systemStartDelimiter

Hi list, A bad value for StaffGroup.systemStartDelimiter appears to cause a segmentation fault: \version "2.19.45" \new StaffGroup \with { systemStartDelimiter = #'aaa } { c'4 } $ lilypond test.ly GNU LilyPond 2.19.45 Processing `traiettorie_ohshit.ly' Parsing... Interpre

Re: Segmentation Fault in music with cueDuring

On 12/29/15 6:58 PM, Simon Albrecht wrote: On 30.12.2015 01:06, Patrick Karl wrote: On 12/29/15 5:53 PM, Simon Albrecht wrote: Hello Pat, this is definitely a bug, I’d say. I’ll write to the bug list. Two or three policy issues with this: 1. Don’t hijack existing threads, if your message has

Re: Segmentation Fault in music with cueDuring

During #"cueNotes" #DOWN R1 } The output looks exactly as I would expect if chords were supported. I think they are supported. And tied notes and tied chords in the quoted music work as expected. The only issue I see is lack of correct implementation of tied individual notes within qu

Re: Segmentation Fault in music with cueDuring

ck of correct > implementation of tied individual notes within quoted chords, resulting in a > segmentation fault. > > (Since quoted chords do work, why doesn't music-quotes-info show them?) Didn't you get http://lists.gnu.org/archive/html/lilypond-user/2015-12/msg00721.html ? `music-quotes-info

Re: Segmentation Fault in music with cueDuring

On 30.12.2015 01:06, Patrick Karl wrote: On 12/29/15 5:53 PM, Simon Albrecht wrote: Hello Pat, this is definitely a bug, I’d say. I’ll write to the bug list. Two or three policy issues with this: 1. Don’t hijack existing threads, if your message has nothing at all to do with their subject.

Re: Segmentation Fault in music with cueDuring

ount 156 [lilypond_serif_3.068359375] Interpreting music...Segmentation fault: 11 The problem appears to be the construct "8 d' " in the cueNotes. Does anyone know why? ___ lilypond-user mailing list lilypond-user@gnu.org https:

Re: Segmentation Fault in music with cueDuring

our message has nothing at all >> to do with their subject. Just compose a new message to the list – >> sorry, but what’s so difficult about that? > > Just out of curiosity, exactly what existing thread do you think I > hijacked? "cue note fontsize inherited by uncued notes?"

Re: Segmentation Fault in music with cueDuring

compiles ok, but if the third \score is uncommented, then lilypond terminates with: . . . Preprocessing graphical objects... Grob count 156 [lilypond_serif_3.068359375] Interpreting music...Segmentation fault: 11 The problem appears to be the construct "8 d'

Re: Segmentation Fault in music with cueDuring

On 30.12.2015 01:38, Thomas Morley wrote: You'll see that only the chord's first note is quoted! Still, the in-chord tie makes the difference, without that tie, the chord is properly quoted. So I’m not sure whether your testing function is useful here. Yours, Simon

Segmentation Fault in music with cueDuring

he third \score is uncommented, then lilypond terminates with: . . . Preprocessing graphical objects... Grob count 156 [lilypond_serif_3.068359375] Interpreting music...Segmentation fault: 11 The problem appears to be the construct "8 d' "

Re: Segmentation Fault in music with cueDuring

On 30.12.2015 00:53, Simon Albrecht wrote: this is definitely a bug, I’d say. I’ll write to the bug list. FWIW, I created a tracker issue directly: How did you get that log output, i.e. how did you invoke LilyPond? Yours, Simon

Re: Segmentation Fault in music with cueDuring

On 12/29/15 5:59 PM, Simon Albrecht wrote: On 30.12.2015 00:53, Simon Albrecht wrote: this is definitely a bug, I’d say. I’ll write to the bug list. FWIW, I created a tracker issue directly: How did you get that log output, i.e. how

Re: Segmentation Fault in music with cueDuring

2015-12-30 0:59 GMT+01:00 Simon Albrecht : > On 30.12.2015 00:53, Simon Albrecht wrote: >> >> this is definitely a bug, I’d say. I’ll write to the bug list. > > > FWIW, I created a tracker issue directly: > > How did

Re: Segmentation Fault in music with cueDuring

2015-12-30 1:45 GMT+01:00 Simon Albrecht : > On 30.12.2015 01:38, Thomas Morley wrote: >> >> You'll see that only the chord's first note is quoted! > > > Still, the in-chord tie makes the difference, without that tie, the chord is > properly quoted. So I’m not sure whether

Re: Segmentation Fault in music with cueDuring

2015-12-30 1:56 GMT+01:00 Thomas Morley : > 2015-12-30 1:45 GMT+01:00 Simon Albrecht : >> On 30.12.2015 01:38, Thomas Morley wrote: >>> >>> You'll see that only the chord's first note is quoted! >> >> >> Still, the in-chord tie makes the

segmentation fault from 2.19.29

I get a segmentation fault from 2.19.29 that I don't get with 2.19.28. I'm running 64-bit on Debian sid. It looks to be size related so a minimal example doesn't seem to be relevant. I'd be happy to run any diagnostic that might help. Paul

Re: segmentation fault from 2.19.29

On Sun, Oct 25, 2015 at 08:15:49PM +0100, David Kastrup wrote: > Paul Scott <waterho...@ultrasw.com> writes: > > > I get a segmentation fault from 2.19.29 that I don't get with > > 2.19.28. I'm running 64-bit on Debian sid. It looks to be size > > related so

Re: segmentation fault from 2.19.29

Paul Scott <waterho...@ultrasw.com> writes: > I get a segmentation fault from 2.19.29 that I don't get with > 2.19.28. I'm running 64-bit on Debian sid. It looks to be size > related so a minimal example doesn't seem to be relevant. Garbage collection while slurs are being p

Re: Make \upbow an empty command + Segmentation fault

Ok, something like upbow = #(make-music 'PostEvents) works with 2.18.2. But I guess there is a less hacky solution. Felix ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Make \upbow an empty command + Segmentation fault

Hi, say I have a violin part with bowing instructions in a variable. Now I want to use the same variable in the full orchestral score but the bowing marks should be suppressed. \upbow is treated by lilypond as an articulation, but the other articulations should be unaffected by the suppressing

Re: Segmentation Fault in 2.18 (was Re: Learn from Finale 2014 (seriously)?)

with a sequence of whole measure rests in the second voice, but it caused a segmentation fault in LilyPond when it tries to merge multi measure rests from both voices. The test file that shows this is attached. The include file is also attached, it is the mergeRests.ly from the original message

Re: Segmentation Fault in 2.18 (was Re: Learn from Finale 2014 (seriously)?)

of whole measure rests in the second voice, but it caused a segmentation fault in LilyPond when it tries to merge multi measure rests from both voices. The test file that shows this is attached. The include file is also attached, it is the mergeRests.ly from the original message

Segmentation Fault in 2.18 (was Re: Learn from Finale 2014 (seriously)?)

, this is taken from some e-mail on this list some time ago. It also merges MultiMeasure rests. I was just putting this code into Denemo and I noticed it merged a multi-measure rest in the top voice with a sequence of whole measure rests in the second voice, but it caused a segmentation fault in LilyPond

Segmentation fault with 2.17.14

I get segmentation faults with 2.17.14 on a medium to large set of files which compile fine with 2.17.13. I have gotten these errors with some other recent 2.17.xx versions. I don't believe I will get errors with a minimal example. What evidence can I provide that might help find the

Re: Segmentation fault with 2.17.14

Paul Scott wrote Wednesday, March 20, 2013 7:56 AM I get segmentation faults with 2.17.14 on a medium to large set of files which compile fine with 2.17.13. I have gotten these errors with some other recent 2.17.xx versions. I don't believe I will get errors with a minimal example.

Re: Segmentation fault with 2.17.14

Trevor Daniels t.dani...@treda.co.uk writes: Paul Scott wrote Wednesday, March 20, 2013 7:56 AM I get segmentation faults with 2.17.14 on a medium to large set of files which compile fine with 2.17.13. I have gotten these errors with some other recent 2.17.xx versions. I don't believe I

Re: Segmentation fault with 2.17.14

Paul Scott waterho...@ultrasw.com writes: I get segmentation faults with 2.17.14 on a medium to large set of files which compile fine with 2.17.13. I have gotten these errors with some other recent 2.17.xx versions. I don't believe I will get errors with a minimal example. What evidence

Re: Segmentation fault with 2.17.14

On Wed, Mar 20, 2013 at 08:37:38AM -, Trevor Daniels wrote: Paul Scott wrote Wednesday, March 20, 2013 7:56 AM I get segmentation faults with 2.17.14 on a medium to large set of files which compile fine with 2.17.13. I have gotten these errors with some other recent 2.17.xx

Re: Segmentation fault with 2.17.14

Paul Scott waterho...@ultrasw.com writes: I appreciate that possibility. I have said the same thing to a number of programming classes I have taught including the assembly language class I was teaching tonight. Sounds like you should be able to run lilypond in a debugger then and get a

Re: Segmentation fault with 2.17.14

Ok. False alarm but hopefully useful info: The error was triggered by two instances of \times which should have been \time . Now my code compiles with either 2.17.13 or 2.17.14. If it helps I am using lilypond-2.17.14-1.linux-64 Maybe this difference between 2.17.14 and 2.17.13 could be

Re: Segmentation fault with 2.17.14

On Wed, Mar 20, 2013 at 10:27:27AM +0100, David Kastrup wrote: Paul Scott waterho...@ultrasw.com writes: I appreciate that possibility. I have said the same thing to a number of programming classes I have taught including the assembly language class I was teaching tonight. Sounds like

Re: Segmentation fault with 2.17.14

Paul Scott waterho...@ultrasw.com writes: Ok. False alarm but hopefully useful info: The error was triggered by two instances of \times which should have been \time . Now my code compiles with either 2.17.13 or 2.17.14. That's no excuse for segfaulting, however. -- David Kastrup

Segmentation fault (core dumped)

Do I send crash reports to this list?___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Segmentation fault (core dumped)

/apc/music$ lilypond WhenILookIntoYourHoliness.ly GNU LilyPond 2.14.2 Processing `WhenILookIntoYourHoliness.ly' Parsing... Interpreting music... Interpreting music... [8][16][24][32]Segmentation fault (core dumped) No core file in that directory. Ubuntu sent a crash report (attached

Re: Segmentation fault (core dumped)

Hi Jeff, On Wed, May 23, 2012 at 9:40 PM, Jeff Barnes jbarnes...@yahoo.com wrote: Do I send crash reports to this list? Not quite. They /usually/ should go to bug-lilyp...@gnu.org . On Wed, May 23, 2012 at 10:03 PM, Jeff Barnes jbarnes...@yahoo.com wrote: Ok, I checked the archives and saw

Re: Segmentation Fault (Midi News Flash)

On Thu, Dec 08, 2011 at 12:23:23AM +, Carl Sorensen wrote: On the other hand, let say I send you the entire choral symphony in a folder. Then you are left going through the syntax looking for the problem. Do you have any suggestions for how this should be fixed? Post a link to your

Segmentation Fault

Hi, I am working on a large score (choral symphony). When I include my tuba part I am getting a segmentation fault. What does this mean? Wouldn't segmentation have to do with a memory issue? Craig Bakalian ___ lilypond-user mailing list lilypond

Re: Segmentation Fault

Le Dec 7, 2011 à 9:12 PM, Craig a écrit : Hi, I am working on a large score (choral symphony). When I include my tuba part I am getting a segmentation fault. What does this mean? Wouldn't segmentation have to do with a memory issue? Craig Bakalian Hey Craig, A segfault usually

Re: Segmentation Fault

Craig wrote: I am working on a large score (choral symphony). When I include my tuba part I am getting a segmentation fault. What does this mean? Wouldn't segmentation have to do with a memory issue? Well, the term is a leftover from the earliest days of Unix, when it ran on machines

Re: Segmentation Fault

Hi Mike, I have found the spot in the tuba part that makes the segmentation fault. And, yes, if I delete or comment out to make the tuba part smaller, lily will write a pdf. Now that I have found the measure, what do I do? I cannot make this project smaller. I would have to send the entire

Re: Segmentation Fault (Midi News Flash)

wrote: Le Dec 7, 2011 à 9:12 PM, Craig a écrit : Hi, I am working on a large score (choral symphony). When I include my tuba part I am getting a segmentation fault. What does this mean? Wouldn't segmentation have to do with a memory issue? Craig Bakalian Hey Craig

Re: Segmentation Fault (Midi News Flash)

, 2011-12-07 at 21:16 +0100, m...@apollinemike.com wrote: Le Dec 7, 2011 à 9:12 PM, Craig a écrit : Hi, I am working on a large score (choral symphony). When I include my tuba part I am getting a segmentation fault. What does this mean? Wouldn't segmentation have to do with a memory

Re: Segmentation Fault

Craig craigbakal...@verizon.net writes: Hi Mike, I have found the spot in the tuba part that makes the segmentation fault. And, yes, if I delete or comment out to make the tuba part smaller, lily will write a pdf. Now that I have found the measure, what do I do? I cannot make

Re: Segmentation Fault

2011/12/7 Craig craigbakal...@verizon.net: Hi Mike, I have found the spot in the tuba part that makes the segmentation fault.  And, yes, if I delete or comment out to make the tuba part smaller, lily will write a pdf. Now that I have found the measure, what do I do?  I cannot make

Re: Segmentation Fault (Midi News Flash)

to compare software and OS versions. You haven't given that information, so we can't do that. Is this segmentation fault due to the number of staves, or the number of notes, or something else? Can you eliminate some of the non-tuba staves, and see if you still get the problem? Can you eliminate some

Re: Segmentation Fault (Midi News Flash)

On Wed, 2011-12-07 at 23:52 +, Carl Sorensen wrote: If you come to the list with very little information and no code available, and ask us what's wrong, we can't possibly tell you. We don't have any idea. This is the main issue with reporting such bugs with lilypond. Let's say I start

Re: Segmentation Fault (Midi News Flash)

On 12/7/11 5:05 PM, Craig craigbakal...@verizon.net wrote: On Wed, 2011-12-07 at 23:52 +, Carl Sorensen wrote: If you come to the list with very little information and no code available, and ask us what's wrong, we can't possibly tell you. We don't have any idea. This is the main

Re: Segmentation Fault (Midi News Flash)

On Wed, Dec 07, 2011 at 07:05:35PM -0500, Craig wrote: This is the main issue with reporting such bugs with lilypond. Let's say I start reducing this problematic file, I reduce the project down to a single file, and then the bug goes away. Then you did a bad job of reducing it. When

Re: Segmentation Fault (Midi News Flash)

Craig craigbakal...@verizon.net writes: On Wed, 2011-12-07 at 23:52 +, Carl Sorensen wrote: If you come to the list with very little information and no code available, and ask us what's wrong, we can't possibly tell you. We don't have any idea. This is the main issue with reporting

Re: Segmentation Fault (Midi News Flash)

On Wed, 7 Dec 2011, Craig wrote: This is the main issue with reporting such bugs with lilypond. Let's say I start reducing this problematic file, I reduce the project down to a single file, and then the bug goes away. I spend hours trying to reduce the project to its point of seg fault.

Completion_heads_engraver produces segmentation fault

The following LY produces a segmentation fault: \version 2.12.3 \layout { \context { \Voice \remove Note_heads_engraver \consists Completion_heads_engraver } } { e'16 ~ e' b' 4 } Does anybody know a workaround or quickfix? Thanks for any advice... .. Here

Re: Completion_heads_engraver produces segmentation fault

(tie_note_candidate_events_[i]-get_property (pitch)); -- View this message in context: http://old.nabble.com/Completion_heads_engraver-produces-segmentation-fault-tp31431579p31431654.html Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com

Re: Completion_heads_engraver produces segmentation fault

- Original Message - From: ornello dominik.hoer...@fun.de To: lilypond-user@gnu.org Sent: Tuesday, April 19, 2011 12:25 PM Subject: Re: Completion_heads_engraver produces segmentation fault Hello again, I thínk there is a wrong index is in completion-note-heads-engraver.cc, line

Re: Completion_heads_engraver produces segmentation fault

On Apr 19, 2011, at 7:25 AM, ornello wrote: Hello again, I thínk there is a wrong index is in completion-note-heads-engraver.cc, line 223: Pitch *p_last = unsmob_pitch (tie_note_candidate_events_[j]-get_property (pitch)); but should be Pitch

Re: segmentation fault with 2.13.32

On Sat 04 Sep 2010, 16:22 Paul Scott wrote: I have reduced the problem to the presence of a \tempo command: \version 2.13.32 \score{ \new StaffGroup \new Staff { %The following line causes a segmentation fault \tempo \markup\bold{ Andante

segmentation fault with 2.13.32

] [century_schoolbook_l_serif_bold_4.869140625] [century_schoolbook_l_serif_bold_italic_6.1357421875] Segmentation fault ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: segmentation fault with 2.13.32

I delete the second staff. I have also attached a verbose output. I have reduced the problem to the presence of a \tempo command: \version 2.13.32 \score{ \new StaffGroup \new Staff { %The following line causes a segmentation fault \tempo \markup

Re: segmentation fault with 2.13.32

On 5 September 2010 00:22, Paul Scott waterho...@ultrasw.com wrote: I have reduced the problem to the presence of a \tempo command: Thanks for the report, Paul. The segfault is triggered by the presence of the full-bar rest in the lower stave: it prevents the setting of a horizontal parent for

Re: Segmentation fault with \revert Stem #'(details beamed-lengths) in \voiceOne

On 22 April 2010 08:20, Rodolfo Zitellini xhero...@gmail.com wrote: Mmh interesting to debug! :) Heh, I guess we're lucky it triggered a segfault as a side effect, otherwise it could've gone unnoticed for even longer. :) Here's the tracker entry:

Re: Segmentation fault with \revert Stem #'(details beamed-lengths) in \voiceOne

On Wed, Apr 21, 2010 at 11:03 PM, Neil Puttock n.putt...@gmail.com wrote: Nasty. :) Thanks for reporting this; I'll add it to the bug tracker once I've done a few more tests. It seems any override for Stem which precedes the nested override triggers the crash.  Looks like there's a bug in

Segmentation fault with \revert Stem #'(details beamed-lengths) in \voiceOne

] \revert Stem #'details #'beamed-lengths s16 [g s g ] | s16 [g s g ] s16 [g s g ] | } \score { \new Staff {\voiceOne \notes } } I get a segmentation fault (bus error). I am using MacOS X 10.5.8 x86. Tried it with lilypond 2.12.1, 2.13.11, 2.13.18

Re: Segmentation fault with \revert Stem #'(details beamed-lengths) in \voiceOne

On 21 April 2010 15:20, Rodolfo Zitellini xhero...@gmail.com wrote: I get a  segmentation fault (bus error). I am using MacOS X 10.5.8 x86. Tried it with lilypond 2.12.1, 2.13.11, 2.13.18. It seems that the problem is generated by the \voiceOne (or \voiveTwo for the matter) - removing

Re: Segmentation fault with \ and \!

cis e16\ cis e cis e8\! | b d16 e a, c e' b d8 r | I get this in the terminal: GNU LilyPond 2.10.33 Processing `file.ly' Parsing... Interpreting music... [8][16][24][32][33] Preprocessing graphical objects...Segmentation fault I have other crescendos and diminuendos in the piece

Re: First scheme program: Preprocessing graphical objects...Segmentation fault

There are some functions (mostly on the C++ side) that assume that the music objects they contain are unique copies, and modify them in place. If objects are shared, functions like going to relative mode and transposition may apply transformations multiple times, laeding to excessive pitches, for

First scheme program: Preprocessing graphical objects...Segmentation fault

objects...Segmentation fault All because I wrote: (append (apply-fingering n2 f1) (append (apply-fingering n2 f2) instead of (append (apply-fingering n1 f1) (append (apply-fingering n2 f2) It appears that any attempt to use the same n object

Re: First scheme program: Preprocessing graphical objects...Segmentation fault

][80][88][96][101] Preprocessing graphical objects...Segmentation fault I've tracked down the cause of the crash. This was caused by a ridiculous number of leger lines. I suspect that the note would not even fit on the page. If you just include just the first six bars you get lots of: programming

Re: First scheme program: Preprocessing graphical objects...Segmentation fault

music... [8][16][24][32][40][48][56][64][72][80][88][96][101] Preprocessing graphical objects...Segmentation fault I've tracked down the cause of the crash. This was caused by a ridiculous number of leger lines. I suspect that the note would not even fit on the page. If you just include just

Re: First scheme program: Preprocessing graphical objects...Segmentation fault

2009/6/20 Tim Woodall lilypond-u...@woodall.me.uk: What am I doing wrong? I can't really explain why it breaks, but repeating a music expression without making a fresh copy can cause weird errors. If you change (append notes notes) to (append notes (ly:music-deep-copy notes)) it works fine.

Re: Segmentation fault on file with bookparts

On 15 dec 2008, at 20:11, Tim Reeves wrote: Also ran successfully here on Win XP SP2, Lilypond 2.11.65, with many warnings. (different from above warnings!) Here on Mac OSX 10.5.5 with lilypond 2.11.65 I also get a whole host of warnings and errors. Most of them are due to font issues:

Re: Segmentation fault on file with bookparts

\version 2.11.65 Segmentfaults with either command lilypond lorca.ly lilypond -V lorca.ly Simon On Mon, 15 Dec 2008 07:25:37 -0600, Jonathan Kulp jonlancek...@gmail.com said: Nicolas Sceaux wrote: I'll try to investigate it soon. Currently my problem is that I can't reproduce these bus

Re: Segmentation fault on file with bookparts

Simon J Mackenzie wrote: \version 2.11.65 Segmentfaults with either command lilypond lorca.ly lilypond -V lorca.ly Simon Thanks for testing, Simon. I tried the -V flag as soon as I read your post but it still segfaulted for me, too. What you said about the \addlyrics command interests

Re: Segmentation fault on file with bookparts

Nicolas Sceaux wrote: I'll try to investigate it soon. Currently my problem is that I can't reproduce these bus errors or seg faults on my machine. Jon, I have problems untaring your archive, only cancioncilla.ly gets untared, can you check if something is wrong with lorca.tar? nicolas

Re: Segmentation fault on file with bookparts

On Mon, Dec 15, 2008 at 5:25 AM, Jonathan Kulp jonlancek...@gmail.com wrote: Yes, I had trouble, too, when I tried downloading it from my site. I think my admin doesn't allow serving of .tar files. Try this one: http://dl4.louisiana.edu/lorca.tar Run lilypond on the lorca.ly file and see

Re: Segmentation fault on file with bookparts

Patrick McCarty wrote: On Mon, Dec 15, 2008 at 5:25 AM, Jonathan Kulp jonlancek...@gmail.com wrote: Yes, I had trouble, too, when I tried downloading it from my site. I think my admin doesn't allow serving of .tar files. Try this one: http://dl4.louisiana.edu/lorca.tar Run lilypond on the

Re: Segmentation fault on file with bookparts

On Mon, Dec 15, 2008 at 7:06 AM, Jonathan Kulp jonlancek...@gmail.com wrote: Patrick McCarty wrote: On Mon, Dec 15, 2008 at 5:25 AM, Jonathan Kulp jonlancek...@gmail.com wrote: Yes, I had trouble, too, when I tried downloading it from my site. I think my admin doesn't allow serving of

Re: Segmentation fault on file with bookparts

I'm using Kubuntu Linux 8.04 Hardy Heron KDE 3.5.10 Linux Kernel 2.6.24-22 generic (i386) Simon On Mon, 15 Dec 2008 09:06:35 -0600, Jonathan Kulp jonlancek...@gmail.com said: Patrick McCarty wrote: On Mon, Dec 15, 2008 at 5:25 AM, Jonathan Kulp jonlancek...@gmail.com wrote: Yes, I had

Re: Segmentation fault on file with bookparts

Simon J Mackenzie wrote: I'm using Kubuntu Linux 8.04 Hardy Heron KDE 3.5.10 Linux Kernel 2.6.24-22 generic (i386) Simon Run lilypond on the lorca.ly file and see what happens. I am able to compile this file successfully. Processing seemed normal, and there were only three types of

Re: Segmentation fault on file with bookparts

: Running 2.11.65, Ubuntu Linux. I'm having problems running a file made up of several bookparts. It looks like it's compiling fine and then it gets to the part where it draws systems and then there's a segmentation fault that kills it. Each of the files runs fine on its own, but gathered

Re: Segmentation fault on file with bookparts

On Mon, Dec 15, 2008 at 8:31 AM, Jonathan Kulp jonlancek...@gmail.com wrote: Well, score one for Windows, I guess. I ran the file successfully on Windows Vista just now. Maybe I should try it with a newer Linux kernel since Patrick compiled it successfully with kernel 2.6.27.8. I'll look

Re: Segmentation fault on file with bookparts

Message: 1 Date: Mon, 15 Dec 2008 07:01:36 -0800 From: Patrick McCarty pnor...@gmail.com Subject: Re: Segmentation fault on file with bookparts To: Jonathan Kulp jonlancek...@gmail.com Cc: lilypond-user lilypond-user@gnu.org Message-ID: d1c3ee7b0812150701o69707465yecb03f6fb9e6a

Re: Segmentation fault on file with bookparts

Graham Percival wrote: See http://www.mail-archive.com/bug-lilyp...@gnu.org/msg13523.html If you could build with debug symbols and provide a backtrace, and/or run lilypond with valgrind, it might help debug it. Cheers, - Graham Graham, I've never used tools like this before and can't

Segmentation fault on file with bookparts

Running 2.11.65, Ubuntu Linux. I'm having problems running a file made up of several bookparts. It looks like it's compiling fine and then it gets to the part where it draws systems and then there's a segmentation fault that kills it. Each of the files runs fine on its own, but gathered

Re: Segmentation fault on file with bookparts

Linux. I'm having problems running a file made up of several bookparts. It looks like it's compiling fine and then it gets to the part where it draws systems and then there's a segmentation fault that kills it. Each of the files runs fine on its own, but gathered into a series

Re: Segmentation fault on file with bookparts

Le 14 déc. 08 à 20:29, Jonathan Kulp a écrit : Running 2.11.65, Ubuntu Linux. I'm having problems running a file made up of several bookparts. It looks like it's compiling fine and then it gets to the part where it draws systems and then there's a segmentation fault that kills it. Each

Re: Segmentation fault on file with bookparts

like it's compiling fine and then it gets to the part where it draws systems and then there's a segmentation fault that kills it. Each of the files runs fine on its own, but gathered into a series of bookparts it fails. From what I've been able to find out reading old postings

Re: Segmentation fault in Lily 2.7.32-3

) and compiled. It fails with this error: [EMAIL PROTECTED]:~/Work_Folder/music/projects/IdaAndDot$ lilypond IdaAndDot.ly GNU LilyPond 2.7.32 Processing `IdaAndDot.ly' Parsing... error: unknown translator: `Parenthesis_engraver' Segmentation fault SHould I forward this to lily-bug? Cam

Segmentation fault in Lily 2.7.32-3

Processing `IdaAndDot.ly' Parsing... error: unknown translator: `Parenthesis_engraver' Segmentation fault SHould I forward this to lily-bug? Cam ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user

segmentation fault

I have installed 2.7.28 on Fedora Core 4. When I try to process a file, I get the following: error: can't open for write: praise.midi: Permission denied /usr/local/bin/lilypond: line 3: 2647 Segmentation fault /usr/local//lilypond/usr/bin/lilypond $@ I saw the Permissioned denied and tried

Segmentation fault

I have tried installing both lilypond-2.6.4.3.x86.package and lilypond-2.7.19.x86.package on Mandrake 10.1. Both installs went smoothly once I figured out that I had to change the permissions to make the file executable. However, when I try to process a file I get a segmentation fault error

Re: Segmentation fault

to process a file I get a segmentation fault error. I've looked around but can't seem to find a specific fix. I did reinstall guile. Did this happen with a particular file, or just *any* file? Like, { c'4 } ? If it's anything, try running lilypond -V foo.ly (where foo.ly is that small snippet

Re: Segmentation fault

the permissions to make the file executable. However, when I try to process a file I get a segmentation fault error. I've looked around but can't seem to find a specific fix. I did reinstall guile. Did this happen with a particular file, or just *any* file? Like, { c'4 } ? If it's

Re: Segmentation Fault

2.4.2 Segmentation fault can you check if it helps to install guile-1.6.7 from http://lilypond.org/download/binaries/Fedora-3/ Thanks. In the meantime, I just re-installed Lilypond, expecting it to segfault again. It didn't. On the other hand, I am not satisfied with Fedora 3. The font

Re: Segmentation Fault

2.4.2 Segmentation fault can you check if it helps to install guile-1.6.7 from http://lilypond.org/download/binaries/Fedora-3/ Thanks. In the meantime, I just re-installed Lilypond, expecting it to segfault again. It didn't. On the other hand, I am not satisfied with Fedora 3. The font

Segmentation Fault

problem, and it worked! I was delighted. The last thing I did before going to bed was to run Lilypond over my bass tablature .ly file. First thing in the morning, if I run Lilypond over ANY .ly file, I get: GNU LilyPond 2.4.2 Segmentation fault I have searched the archives and it seems

Segmentation Fault

to eliminate the feta20.afm problem, and it worked! I was delighted. The last thing I did before going to bed was to run Lilypond over my bass tablature .ly file. First thing in the morning, if I run Lilypond over ANY .ly file, I get: GNU LilyPond 2.4.2 Segmentation fault can you check