2018-02-05 23:48 GMT+01:00 David Kastrup <d...@gnu.org>:
> Thomas Morley <thomasmorle...@gmail.com> writes:
>
>> 2018-02-05 23:23 GMT+01:00 David Kastrup <d...@gnu.org>:
>>
>>>
>>> Uh, you are aware that your log ends with:
>>>
>>> Writing ./f4/lily-265fe61c-systems.count...Segmentation fault (core dumped)
>>>
>>> The programming errors are a nuisance (and should likely get fixed) but
>>> this aborts for entirely different reasons.
>>
>> Yes, but ofcourse a segfault has a reason and the programming errors
>> were the only other messages.
>>
>> Any hint to track it down?
>
> set ulimit -c 1000000
>
> (core dump size limit to 1000000 kbytes) and try again.  Then look in
> your tree for a file called "core" and call
>
> gdb out/bin/lilypond path/to/core
>
> and then try
>
> backtrace
>
> in the debugger.  It's probably not trivial to figure out what file is
> responsible, but at least one will be able to figure out what happens.
>
> --
> David Kastrup

Thanks, I'll try tomorrow.

Unless I can't sleep tonight ....

Cheers,
  Harm

_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Reply via email to