Segmentation fault: \addquote chokes on \new Voice

2006-10-11 Thread Marcus Macauley
I haven't upgraded to Lilypond 2.9.22 yet, but the following file generates a segmentation fault for me on Lilypond 2.9.17 (Linux). Hopefully someone can run it on 2.9.22 to confirm that the bug still exists, or I'll repost once I've upgraded. Marcus \version "2.9.17" % When lilypond is

Re: Segmentation fault: \addquote chokes on \new Voice

2006-10-11 Thread Marcus Macauley
I just upgraded to 2.9.22 (for Linux), and this bug persists. So here it is again (below) with the proper version number. Marcus \version "2.9.22" % When lilypond is run on this file, it generates a segmentation fault. % Apparently \addquote can't handle the \new Voice. % % The documentation

Re: Segmentation fault: \addquote chokes on \new Voice

2006-10-11 Thread Han-Wen Nienhuys
Marcus Macauley schreef: I just upgraded to 2.9.22 (for Linux), and this bug persists. So here it is again (below) with the proper version number. http://code.google.com/p/lilypond/issues/detail?id=111 Erik, I believe this may be related to your changes. Can you have a look at this? Thanks

Re: Segmentation fault: \addquote chokes on \new Voice

2006-10-16 Thread Erik Sandberg
On Thursday 12 October 2006 01:53, Han-Wen Nienhuys wrote: > Marcus Macauley schreef: > > I just upgraded to 2.9.22 (for Linux), and this bug persists. > > > > So here it is again (below) with the proper version number. > > http://code.google.com/p/lilypond/issues/detail?id=111 > > Erik, > > I beli

Re: Segmentation fault: \addquote chokes on \new Voice

2006-10-16 Thread Han-Wen Nienhuys
Erik Sandberg schreef: The attached patch fixes this. The problem is that context::implementation isn't initialised. They don't need to be, because quote and friends use non-translator listeners. The patch inserts checks for implementation_ != 0 everywhere. I wanted to do it like this, but I

Re: Segmentation fault: \addquote chokes on \new Voice

2006-10-16 Thread Erik Sandberg
On Tuesday 17 October 2006 00:02, Han-Wen Nienhuys wrote: > Erik Sandberg schreef: > > The attached patch fixes this. > > > > The problem is that context::implementation isn't initialised. They don't > > need to be, because quote and friends use non-translator listeners. The > > patch inserts check

Re: Segmentation fault: \addquote chokes on \new Voice

2006-10-16 Thread Erik Sandberg
On Tuesday 17 October 2006 00:02, Han-Wen Nienhuys wrote: > Erik Sandberg schreef: > > The attached patch fixes this. > > > > The problem is that context::implementation isn't initialised. They don't > > need to be, because quote and friends use non-translator listeners. The > > patch inserts check

Re: Segmentation fault: \addquote chokes on \new Voice

2006-10-17 Thread Han-Wen Nienhuys
Erik Sandberg schreef: On Tuesday 17 October 2006 00:02, Han-Wen Nienhuys wrote: Erik Sandberg schreef: The attached patch fixes this. The problem is that context::implementation isn't initialised. They don't need to be, because quote and friends use non-translator listeners. The patch inserts

Re: Segmentation fault: \addquote chokes on \new Voice

2006-10-18 Thread Han-Wen Nienhuys
Erik Sandberg schreef: On Thursday 12 October 2006 01:53, Han-Wen Nienhuys wrote: Marcus Macauley schreef: I just upgraded to 2.9.22 (for Linux), and this bug persists. So here it is again (below) with the proper version number. http://code.google.com/p/lilypond/issues/detail?id=111 Erik, I

Re: Segmentation fault: \addquote chokes on \new Voice

2006-10-18 Thread Erik Sandberg
On Wednesday 18 October 2006 10:12, Han-Wen Nienhuys wrote: > Erik Sandberg schreef: > > On Thursday 12 October 2006 01:53, Han-Wen Nienhuys wrote: > Thanks for fixing this; can you update issue #111 and add a fixed2925 tag? Done. Should I mark somehow that I'm the one who fixed it (through 'Owne

Re: Segmentation fault: \addquote chokes on \new Voice

2006-10-18 Thread Han-Wen Nienhuys
Erik Sandberg schreef: On Wednesday 18 October 2006 10:12, Han-Wen Nienhuys wrote: Erik Sandberg schreef: On Thursday 12 October 2006 01:53, Han-Wen Nienhuys wrote: Thanks for fixing this; can you update issue #111 and add a fixed2925 tag? Done. Should I mark somehow that I'm the one who f