On Fri, Oct 22, 2010 at 6:06 AM, Valentin Villenave
wrote:
> On Fri, Oct 22, 2010 at 3:02 PM, Carl Sorensen wrote:
>> As near as I can tell, this code is triggering an infinite loop that fails
>> when the scheme heap overflows.
>
> Interesting.
>
>> arg is *not* a stream-event, it's a music-event
On Fri, Oct 22, 2010 at 3:02 PM, Carl Sorensen wrote:
> As near as I can tell, this code is triggering an infinite loop that fails
> when the scheme heap overflows.
Interesting.
> arg is *not* a stream-event, it's a music-event.
Indeed. But I wasn't expecting it to cause a segfault.
> Segfault
On 10/22/10 3:10 AM, "Valentin Villenave" wrote:
> The following code causes a segfault.
> LilyPond 2.13.36, GNU/Linux x86_64.
>
> toto =
> #(define-music-function (parser location arg) (ly:music?)
>(display (ly:event-property arg 'name))
>(make-sequential-music arg))
>
> { \toto a }
The following code causes a segfault.
LilyPond 2.13.36, GNU/Linux x86_64.
toto =
#(define-music-function (parser location arg) (ly:music?)
(display (ly:event-property arg 'name))
(make-sequential-music arg))
{ \toto a }
Also reproduced with today's git.
--verbose output isn't of any help:
