Issue 433 in lilypond: 2.11.30 segmentation fault
Issue 433: 2.11.30 segmentation fault http://code.google.com/p/lilypond/issues/detail?id=433 Comment #6 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 433 in lilypond: 2.11.30 segmentation fault
Issue 433: 2.11.30 segmentation fault http://code.google.com/p/lilypond/issues/detail?id=433 Comment #5 by trevorbaca: Graham, Hooray! It's fixed on my side under OS X Intel. Outstanding. I no longer have to chunk up my complex files; everything runs 100% Trevor. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 433 in lilypond: 2.11.30 segmentation fault
Issue 433: 2.11.30 segmentation fault http://code.google.com/p/lilypond/issues/detail?id=433 Comment #4 by gpermus: Trevor, could you test with 2.11.34? I can't verify this myself, since I don't have the input file. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 433 in lilypond: 2.11.30 segmentation fault
Issue 433: 2.11.30 segmentation fault http://code.google.com/p/lilypond/issues/detail?id=433 Comment #3 by gpermus: Trevor, could you test with 2.11.34? I can't verify this myself, since I don't have the input file. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 433 in lilypond: 2.11.30 segmentation fault
Issue 433: 2.11.30 segmentation fault http://code.google.com/p/lilypond/issues/detail?id=433 Comment #2 by joeneeman: (No comment was entered for this change.) Issue attribute updates: Status: Fixed Labels: fixed_2_11_34 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 433 in lilypond: 2.11.30 segmentation fault
Issue 433: 2.11.30 segmentation fault http://code.google.com/p/lilypond/issues/detail?id=433 Comment #1 by aurelien.bello: Hi, I got the same problem with a large file (more of 600 bars of hard-coded music) using 2.11.32. After a while computing the programm gives up. In verbose mode I got "segmentation fault" as last message. The problem does not appear if I use 2.11.28. Maybe it will help to go back to this version... The piece I'm writing is a large orchestral piece. I join you 3 files : "common.ly", which I use to store variables for all pieces ; "basson.ly", the bassoon part, which works fine with 2.11.32 "alto.ly", using the same "common.ly" canvas, but giving a crash with 2.11.32 and working fine with version until 2.11.28. I use mac os 10.4. on an Intel machine. Best regards, Aurélien Bello Attachments: common.ly 7.9 KB alto.ly 14.3 KB basson.ly 5.6 KB -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: 2.11.30 segmentation fault
On 9/2/07, Nicolas Sceaux <[EMAIL PROTECTED]> wrote: > Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: > > > Joe Neeman escreveu: > >> On Saturday 01 September 2007 09:00, Trevor Bača wrote: > >>> On 8/31/07, Joe Neeman <[EMAIL PROTECTED]> wrote: > On Friday 31 August 2007 23:17, Trevor Bača wrote: > > Should I send the inputfile to either Joe or Han-Wen for testing > > against .31? > I'd be happy to take a look at it. > >>> Thank you *so* much, Joe! Will send offlist ... > >> > >> I can't reproduce with git or the x86-linux binary. > >> I get a segfault with the amd64 binary... in ghostscript (during the > >> convert-to-pdf stage). If I take the .ps file and run it though the > >> system's > >> ghostscript, it works perfectly. So it seems to be a problem with the > >> ghostscript that's included in the binary package. > > > > In the original report, it didn't crash in GS but in lily. > > It looks as if someone needs to build a macos binary without > > stripping. > > I have such a beast here, maybe Trevor could send me his failing file. Excellent! I'll send you the file offlist in just a second ... and you can feed it to the beast ;-) -- Trevor Bača [EMAIL PROTECTED] ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: 2.11.30 segmentation fault
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: > Joe Neeman escreveu: >> On Saturday 01 September 2007 09:00, Trevor Bača wrote: >>> On 8/31/07, Joe Neeman <[EMAIL PROTECTED]> wrote: On Friday 31 August 2007 23:17, Trevor Bača wrote: > Should I send the inputfile to either Joe or Han-Wen for testing > against .31? I'd be happy to take a look at it. >>> Thank you *so* much, Joe! Will send offlist ... >> >> I can't reproduce with git or the x86-linux binary. >> I get a segfault with the amd64 binary... in ghostscript (during the >> convert-to-pdf stage). If I take the .ps file and run it though the system's >> ghostscript, it works perfectly. So it seems to be a problem with the >> ghostscript that's included in the binary package. > > In the original report, it didn't crash in GS but in lily. > It looks as if someone needs to build a macos binary without > stripping. I have such a beast here, maybe Trevor could send me his failing file. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: 2.11.30 segmentation fault
Joe Neeman escreveu: > On Saturday 01 September 2007 09:00, Trevor Bača wrote: >> On 8/31/07, Joe Neeman <[EMAIL PROTECTED]> wrote: >>> On Friday 31 August 2007 23:17, Trevor Bača wrote: Should I send the inputfile to either Joe or Han-Wen for testing against .31? >>> I'd be happy to take a look at it. >> Thank you *so* much, Joe! Will send offlist ... > > I can't reproduce with git or the x86-linux binary. > I get a segfault with the amd64 binary... in ghostscript (during the > convert-to-pdf stage). If I take the .ps file and run it though the system's > ghostscript, it works perfectly. So it seems to be a problem with the > ghostscript that's included in the binary package. In the original report, it didn't crash in GS but in lily. It looks as if someone needs to build a macos binary without stripping. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: 2.11.30 segmentation fault
On Saturday 01 September 2007 09:00, Trevor Bača wrote: > On 8/31/07, Joe Neeman <[EMAIL PROTECTED]> wrote: > > On Friday 31 August 2007 23:17, Trevor Bača wrote: > > > Should I send the inputfile to either Joe or Han-Wen for testing > > > against .31? > > > > I'd be happy to take a look at it. > > Thank you *so* much, Joe! Will send offlist ... I can't reproduce with git or the x86-linux binary. I get a segfault with the amd64 binary... in ghostscript (during the convert-to-pdf stage). If I take the .ps file and run it though the system's ghostscript, it works perfectly. So it seems to be a problem with the ghostscript that's included in the binary package. Joe ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: 2.11.30 segmentation fault
2007/9/1, Trevor Bača <[EMAIL PROTECTED]>: > > Joe's looking at the inputfile, which is awesome. > > For future reference, is there any way to get an unstripped binary > (one with all the debug messages not commented out, right?) from the > website? Or is git the only way to go? (I've so far avoided using git > because I've not been contributing patches; but I'm certainly > comfortable running stuff in gdb if it would help.) Git is the only way to go; it's unfortunate, because compiling lilypond is such a PITA. We could look into making debug info available separately for the binary builds, but it would take a lot of space, for rare occasions. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: 2.11.30 segmentation fault
On 8/31/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote: > 2007/8/31, Trevor Bača <[EMAIL PROTECTED]>: > > Hi, > > > > Crossposted as Google #433. > > > > Running 2.11.30 on a relatively large file (110 measures of six staves > > with 4559 lines of total input) causes the following segmentation > > fault. > > > > > > > GNU LilyPond 2.11.30 > > Processing `/Users/trevorbaca/Documents/lilypond/pictures/1768.ly' > > Parsing... > > Interpreting music... [8][16][24] > > Preprocessing graphical > > objects.../Users/trevorbaca/Documents/lascaux/scr/lily: line 4: 14270 > > Segmentation fault > > > > > > I've been cutting out parts of the file all morning to produce a > > minimal snippet. But at this point it appears that the seg fault comes > > from the *size* of the inputfile rather than from the *musical > > contents*. (Ie, file compiles absolutely fine to and with measure 109; > > adding measure 110 *in any of the six musical staves* causes the seg > > fault.) > > One way of finding this out is to run the thing inside GDB and look at > the stack trace. Unfortunately, for useful information, you have to > do this in an unstripped binary, which is not included in the > installer. Joe's looking at the inputfile, which is awesome. For future reference, is there any way to get an unstripped binary (one with all the debug messages not commented out, right?) from the website? Or is git the only way to go? (I've so far avoided using git because I've not been contributing patches; but I'm certainly comfortable running stuff in gdb if it would help.) -- Trevor Bača [EMAIL PROTECTED] ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: 2.11.30 segmentation fault
On 8/31/07, Joe Neeman <[EMAIL PROTECTED]> wrote: > On Friday 31 August 2007 23:17, Trevor Bača wrote: > > Should I send the inputfile to either Joe or Han-Wen for testing against > > .31? > > I'd be happy to take a look at it. Thank you *so* much, Joe! Will send offlist ... Trevor. -- Trevor Bača [EMAIL PROTECTED] ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: 2.11.30 segmentation fault
On Friday 31 August 2007 23:17, Trevor Bača wrote: > Should I send the inputfile to either Joe or Han-Wen for testing against > .31? I'd be happy to take a look at it. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: 2.11.30 segmentation fault
2007/8/31, Trevor Bača <[EMAIL PROTECTED]>: > Hi, > > Crossposted as Google #433. > > Running 2.11.30 on a relatively large file (110 measures of six staves > with 4559 lines of total input) causes the following segmentation > fault. > > GNU LilyPond 2.11.30 > Processing `/Users/trevorbaca/Documents/lilypond/pictures/1768.ly' > Parsing... > Interpreting music... [8][16][24] > Preprocessing graphical > objects.../Users/trevorbaca/Documents/lascaux/scr/lily: line 4: 14270 > Segmentation fault > > > I've been cutting out parts of the file all morning to produce a > minimal snippet. But at this point it appears that the seg fault comes > from the *size* of the inputfile rather than from the *musical > contents*. (Ie, file compiles absolutely fine to and with measure 109; > adding measure 110 *in any of the six musical staves* causes the seg > fault.) One way of finding this out is to run the thing inside GDB and look at the stack trace. Unfortunately, for useful information, you have to do this in an unstripped binary, which is not included in the installer. Usually segfaults are writing to a null pointer, and I remember doing 500 mesaures of 64 staves without problems, so memory overflow seems unlikely. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: 2.11.30 segmentation fault
On 8/31/07, Valentin Villenave <[EMAIL PROTECTED]> wrote: > 2007/8/31, Trevor Bača <[EMAIL PROTECTED]>: > > Hi, > > > > Crossposted as Google #433. > > Hi Trevor, > I don't know if you've suscribed to the bug-lilypond list (if you have > not, I can tell you it is very interesting), but it seems that each > issue posted on Google (and each comment, or attribute changes) is > forwarded to the bug- list; so I don't think you have to cross-post > anymore. (the opposite is not true: a mail to bug- won't be forwarded > to the google tracker, unless some generous soul adds it). OK, very good. I am subscribed to bug-. But I thought that I received forwarded copies of the bugs I opened because I opened them (rather than because everything forwards to bug-). Good to know. -- Trevor Bača [EMAIL PROTECTED] ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: 2.11.30 segmentation fault
2007/8/31, Trevor Bača <[EMAIL PROTECTED]>: > Hi, > > Crossposted as Google #433. Hi Trevor, I don't know if you've suscribed to the bug-lilypond list (if you have not, I can tell you it is very interesting), but it seems that each issue posted on Google (and each comment, or attribute changes) is forwarded to the bug- list; so I don't think you have to cross-post anymore. (the opposite is not true: a mail to bug- won't be forwarded to the google tracker, unless some generous soul adds it). Regards, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
2.11.30 segmentation fault
Hi, Crossposted as Google #433. Running 2.11.30 on a relatively large file (110 measures of six staves with 4559 lines of total input) causes the following segmentation fault. GNU LilyPond 2.11.30 Processing `/Users/trevorbaca/Documents/lilypond/pictures/1768.ly' Parsing... Interpreting music... [8][16][24] Preprocessing graphical objects.../Users/trevorbaca/Documents/lascaux/scr/lily: line 4: 14270 Segmentation fault I've been cutting out parts of the file all morning to produce a minimal snippet. But at this point it appears that the seg fault comes from the *size* of the inputfile rather than from the *musical contents*. (Ie, file compiles absolutely fine to and with measure 109; adding measure 110 *in any of the six musical staves* causes the seg fault.) Should I send the inputfile to either Joe or Han-Wen for testing against .31? (Note: not related to Google #430 which Han-Wen has already fixed.) -- Trevor Bača [EMAIL PROTECTED] ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 433 in lilypond: 2.11.30 segmentation fault
Issue 433: 2.11.30 segmentation fault http://code.google.com/p/lilypond/issues/detail?id=433 New issue report by trevorbaca: Hi, Running 2.11.30 on a relatively large file (110 measures of six staves with 4559 lines of total input) causes the following segmentation fault. GNU LilyPond 2.11.30 Processing `/Users/trevorbaca/Documents/lilypond/pictures/1768.ly' Parsing... Interpreting music... [8][16][24] Preprocessing graphical objects.../Users/trevorbaca/Documents/lascaux/scr/lily: line 4: 14270 Segmentation fault I've been cutting out parts of the file all morning to produce a minimal snippet. But at this point it appears that the seg fault comes from the *size* of the inputfile rather than from the *musical contents*. (Ie, file compiles absolutely fine to and with measure 109; adding measure 110 *in any of the six musical staves* causes the seg fault.) Should I send the inputfile to either Joe or Han-Wen for testing against .31? (Note: not related to Google #430 which Han-Wen has already fixed.) Issue attributes: Status: New Owner: Labels: Type-Defect Priority-Medium -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
