Urs Liska <[email protected]> writes:
> Am 31. Juli 2016 15:10:54 MESZ, schrieb Andrew Bernard
> <[email protected]>:
>>I am reluctant to even mention it, but a perfectly OK score that runs
>>fine on 2.19.45 now seg faults on 2.19.46.
>>
>>is there any change that is known to cause such behaviour? I am unable
>>to discern what it may be, since my code is unchanged. Running on
>>openSUSE Leap 42.1.
>>
>>$? is 139. [A clue?]
That's just a standard segfault (128+11, with 11 being
SIGSEGV 11 Core Invalid memory reference
).
>>What do I need to provide to help understand this?
>
> Start running with the --verbose option.
That's somewhat more helpful but it usually is a lot more helpful
running in gdb, like
gdb lilypond # or possibly gdb64 lilypond
run --verbose somefile.ly
(now you are likely returning to the debugger prompt with a SIGSEGV)
backtrace
and then copy and paste the backtrace (may require pressing RETURN a few
times before the whole backtrace appears) and a bit of the debug output
from LilyPond before that.
--
David Kastrup
_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond
