[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Strange error with no traceable cause.
From: |
David Kastrup |
Subject: |
Re: Strange error with no traceable cause. |
Date: |
Tue, 05 Jun 2018 23:35:34 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
Karlin High <address@hidden> writes:
> On 6/5/2018 4:02 PM, Thomas Morley wrote:
>>> For running gdb do:
>>>
>>> gdb path/to/lilypond-executable
>>>
>>> For example: gdb lilypond-git/build/out/bin/lilypond
>>> You will get some infos about gdb returned, finally it ends with
>>> (gdb)
>>>
>>> Then type:
>>> run path/to/the/ly-file
>> I forgot, type:
>>
>> bt
>>
>> to get the stack and then:
>>
>>> Post the output.
>
> Watching and learning about gdb... Does this work for "standard"
> LilyPond distributions? Or only for compiled-from-source with
> debugging symbols or something?
The backtrace usually at least is good for the function names even
without debug information.
--
David Kastrup
- Strange error with no traceable cause., crimsonsunrise, 2018/06/05
- Re: Strange error with no traceable cause., David Kastrup, 2018/06/05
- Re: Strange error with no traceable cause., crimsonsunrise, 2018/06/05
- Re: Strange error with no traceable cause., David Kastrup, 2018/06/05
- Re: Strange error with no traceable cause., crimsonsunrise, 2018/06/05
- Re: Strange error with no traceable cause., David Kastrup, 2018/06/05
- Re: Strange error with no traceable cause., crimsonsunrise, 2018/06/05
- Re: Strange error with no traceable cause., Thomas Morley, 2018/06/05
- Re: Strange error with no traceable cause., Thomas Morley, 2018/06/05
- Re: Strange error with no traceable cause., Karlin High, 2018/06/05
- Re: Strange error with no traceable cause.,
David Kastrup <=