Re: wrt 'Make doc crashing on my PC'

[Phil Holmes]

I repeatedly get a failed make doc on orchestra.ly.  Making almost any change to the file allows make doc to complete.  Compiling orchestra.ly in standalone mode also works OK.  I've taken to getting a successful make doc using an edited orchestra.ly and then doing incremental makes.  It does mean, however, that I can't run patchy.

--
Phil Holmes

 

 

----- Original Message -----

From: James

To: address@hidden

Sent: Thursday, August 08, 2013 1:27 PM

Subject: Re: wrt 'Make doc crashing on my PC'

hello,

On 08/08/13 12:47, Petr Gajdos wrote:

Reply to 'Make doc crashing on my PC' thread started on 22 Jun 2013.

Hi list,

I have same symptomps like Phil described.

Snippet of build log:
---------------------8<--------------------------
 /home/abuild/rpmbuild/BUILD/lilypond-2.17.23/scripts/build/out/run-and-check
"/usr/bin/lilypond -dpreview -dresolution=150 -o ./out-www
orchestra.ly" "orchestra.preview.log"

 Please check the logfile orchestra.preview.log for errors

 make[2]: *** [out-www/orchestra.png] Error 139
--------------------->8--------------------------

orchestra.preview.log contents
---------------------8<--------------------------
Changing working directory to: `./out-www'
Processing `orchestra.ly'
Parsing...
Interpreting music...
Preprocessing graphical
objects.../home/abuild/rpmbuild/BUILD/lilypond-2.17.23/scripts/build/out/run-and-check:
line 6:   778 Segmentation fault      (core dumped) /usr/bin/lilypond
-dpreview -dresolution=150 -o ./out-www orchestra.ly
--------------------->8--------------------------

Backtrace attached.

I would happy to help with more debugging, just tell how.

Petr

_______________________________________________
lilypond-devel mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-devel

I seem to recall that this was something 'leaking' out of the compilation of this file (as David K put it) that caused one of his (unrelated) patches to also fail like this while I was patch testing a few weeks back, but I cannot find the tracker as I normally put the error message when I find a problem with any patch.

There seems to be something random with this .ly file.

I only use 32 bit (old skool lilydev - Ubuntu 11:04).

But it didn't happen again on subsequent compilations.

James

---

_______________________________________________
lilypond-devel mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-devel