lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: another slur problem


From: David Kastrup
Subject: Re: another slur problem
Date: Tue, 05 Jul 2016 12:32:23 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux)

Martin Tarenskeen <address@hidden> writes:

> On Tue, 5 Jul 2016, David Kastrup wrote:
>
>>>> Probably GCC6.  What does ldd /usr/bin/lilypond state?
>>>
>>> See attachment.
>>
>> Huh.  The library version numbers (including C++ library as far as I can
>> tell) seem to match those of my system pretty closely.  Can you run this
>> under the debugger and get a traceback of the segfault?
>>
>> Basically
>>
>> gdb64 lilypond
>> run /tmp/bad-file.ly
>> backtrace
>>
>> It's gdb64 on my rather promiscous system.  Could be just gdb on yours.
>>
>
> See attached gdb.txt

Starting program: /usr/bin/lilypond slurtest2.ly
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x000055555561fa4f in Grob::get_offset (address@hidden, 
    address@hidden) at grob.cc:400
400       if (dim_cache_[a].offset_)
#0  0x000055555561fa4f in Grob::get_offset(Axis) const (address@hidden, 
address@hidden) at grob.cc:400
#1  0x000055555561fb48 in Grob::relative_coordinate(Grob const*, Axis) const 
(this=0x0, refp=0x55555619f290, a=X_AXIS) at grob.cc:341
#2  0x000055555561fb6e in Grob::relative_coordinate(Grob const*, Axis) const 
(this=0x55555619eda0, refp=0x55555619f290, a=X_AXIS) at grob.cc:345

Looks rather like

https://sourceforge.net/p/testlilyissues/issues/4814/

-- 
David Kastrup



reply via email to

[Prev in Thread] Current Thread [Next in Thread]