Re: multiple fret-diagram-x markup commands and lilypond-book safe-mode

[Julien Rioux]

On 15/11/2010 10:54 PM, Patrick McCarty wrote:
> Hi Julien,
>
> On 2010-11-15, Julien Rioux wrote:
> > On 15/11/2010 2:59 PM, Patrick McCarty wrote:
> > > Compiling with debug flags*might*  help to narrow down the issue.  The
> > > easiest way to compile without optimization is by running autogen.sh
> > > like so
> > >
> > >    ./autogen.sh --disable-optimising
> >
> > I have done this now, and get the problem again, with little more
> > information on screen. Attached is a log of the output on the
> > terminal. I don't understand this output but hope it might help.
>
> Hmm, the only important difference I see in your logs is this:
>
> -Wrong type argument in position 1 (expecting module): #<srcprops ((breakpoint . #f) (line . 
> 602) (column . 58) (filename . 
> "/usr/local/share/lilypond/2.13.39/ly/music-functions-init.ly"))>
> +Wrong type argument in position 1 (expecting module): #<unknown-type (0xb0227 . 
> 0x74726170) @ 0xb68ef940>
>
> These types of errors are very similar to those I've been encountering
> when compiling against the development version of Guile (1.9).
>
> I've never seen them with Guile 1.8 though...
>
> > Next step is compiling guile, I guess.
>
> Yes, I think that would be the best thing to do.
>
> Hopefully we will figure this out soon!
>
> Thanks,
> Patrick


After dumping guile 1.8.7 provided by the official ubuntu repository, I 
downloaded, compiled and installed the latest stable guile 1.8.8 and 
recompiled latest lilypond git. I still get the failure.

I simplified the test case by taking lilypond-book out of the process. 
The attached contains two lilypond snippets which compile correctly with 
independent calls

lilypond -dbackend=eps snippet-1.ly
lilypond -dbackend=eps snippet-2.ly

, but combining them in a single call with

lilypond -dbackend=eps -dread-file-list snippet-names.ly

exits with an error when processing the second snippet. It's as if some 
state has changed inbetween processing the two snippets, and the parsing 
goes awry on the second one. This happens with other examples as well, 
and on another ubuntu machine. Sometimes I get a segfault, but most of 
the time lilypond just quits with the error, although the file is valid 
lilypond code. Whatever I have tried, I can't make it to compile the two 
snippets.

--
Julien

output.log
Description: Text document

safe-mode-bug.tar
Description: Unix tar archive