Re: crash moving DotColumn

[David Kastrup]

Thomas Morley <address@hidden> writes:

> 2016-05-10 11:28 GMT+02:00 Thomas Morley <address@hidden>:
>
>>>
>>> Can you give a full backtrace from the debugger?  Likely something like
>>>
>>> gdb out/bin/lilypond
>>> run /tmp/foo-test-file.ly
>>> bt
>>>
>>> should do the trick.
>>
>> Will try in the evening, have to run.
>
>
> Hope I did it correctly, never used gdb before.
> See attached.
>
> Cheers,
>   Harm
>
> (gdb) bt
> #0  0x00007ffff5dd1418 in __GI_raise (address@hidden) at 
> ../sysdeps/unix/sysv/linux/raise.c:54
> #1  0x00007ffff5dd301a in __GI_abort () at abort.c:89
> #2  0x00007ffff5dc9bd7 in __assert_fail_base (fmt=<optimized out>, 
>     address@hidden "scm_is_null (value) || scm_is_eq (value, marker)", 
>     address@hidden "/home/hermann/lilypond-git/lily/grob-property.cc", 
> address@hidden, 
>     address@hidden <Grob::try_callback_on_alist(scm_unused_struct**, 
> scm_unused_struct*, scm_unused_struct*)::__PRETTY_FUNCTION__> 
> "scm_unused_struct* Grob::try_callback_on_alist(scm_unused_struct**, SCM, 
> SCM)") at assert.c:92
> #3  0x00007ffff5dc9c82 in __GI___assert_fail (address@hidden "scm_is_null 
> (value) || scm_is_eq (value, marker)", 
>     address@hidden "/home/hermann/lilypond-git/lily/grob-property.cc", 
> address@hidden, 
>     address@hidden <Grob::try_callback_on_alist(scm_unused_struct**, 
> scm_unused_struct*, scm_unused_struct*)::__PRETTY_FUNCTION__> 
> "scm_unused_struct* Grob::try_callback_on_alist(scm_unused_struct**, SCM, 
> SCM)") at assert.c:101
> #4  0x000000000068a19d in Grob::try_callback_on_alist (proc=<optimized out>, 
> sym=0x7ffff20318e0, alist=0xe867a0, this=0xe86740)
>     at /home/hermann/lilypond-git/lily/grob-property.cc:242

[...]

Phoo.  Yes, you did it correctly.  That one gives me a headache: I'll
have to get back to it tomorrow.  Looks like several callbacks calling
one another in circular fashion, but I'm not completely sure.

-- 
David Kastrup