David Kastrup writes:
> Thomas Morley writes:
>
>> commit d6e93146b9f25e914373caeced7314237cc53e2f
>> (Don't remember which optimizing-option I used, though)
>>
>> gdb says
>> Program received signal SIGSEGV, Segmentation fault.
>> 0x004ae5ab in Grob::get_offset (a=X_AXIS, this=0x0) at
>
David Kastrup writes:
> At any rate, try a backtrace so that we figure out which function is
> responsible for the "this" pointer being 0.
Embarrassing. I see that you already did.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
Thomas Morley writes:
>> I can confirm the bug with a build from
>> commit d6e93146b9f25e914373caeced7314237cc53e2f
>> (Don't remember which optimizing-option I used, though)
>>
>> gdb says
>> Program received signal SIGSEGV, Segmentation fault.
>> 0x004ae5ab in Grob::get_offset (a=X_AXIS
Thomas Morley writes:
> commit d6e93146b9f25e914373caeced7314237cc53e2f
> (Don't remember which optimizing-option I used, though)
>
> gdb says
> Program received signal SIGSEGV, Segmentation fault.
> 0x004ae5ab in Grob::get_offset (a=X_AXIS, this=0x0) at
> /home/hermann/lilypond-git/lily/
2016-09-02 20:51 GMT+02:00 Thomas Morley :
> 2016-09-02 20:12 GMT+02:00 David Kastrup :
>> Timothy Lanfear writes:
>>
>>> On 02/09/16 17:31, David Kastrup wrote:
Timothy Lanfear writes:
> Bug appears in 2.19.46 and .47. Ubuntu 16.04, 64-bit.
>
> The first line provokes a cor
2016-09-02 20:12 GMT+02:00 David Kastrup :
> Timothy Lanfear writes:
>
>> On 02/09/16 17:31, David Kastrup wrote:
>>> Timothy Lanfear writes:
>>>
Bug appears in 2.19.46 and .47. Ubuntu 16.04, 64-bit.
The first line provokes a core dump. The second line is perhaps the
right syn
Timothy Lanfear writes:
> On 02/09/16 17:31, David Kastrup wrote:
>> Timothy Lanfear writes:
>>
>>> Bug appears in 2.19.46 and .47. Ubuntu 16.04, 64-bit.
>>>
>>> The first line provokes a core dump. The second line is perhaps the
>>> right syntax for this construction and works fine, but I'm rep
On 02.09.2016 18:00, Timothy Lanfear wrote:
Bug appears in 2.19.46 and .47. Ubuntu 16.04, 64-bit.
I can confirm. 2.19.45 is fine.
The first line provokes a core dump. The second line is perhaps the
right syntax for this construction and works fine, but I'm reporting
in case there is someth
On 02/09/16 17:31, David Kastrup wrote:
Timothy Lanfear writes:
Bug appears in 2.19.46 and .47. Ubuntu 16.04, 64-bit.
The first line provokes a core dump. The second line is perhaps the
right syntax for this construction and works fine, but I'm reporting
in case there is something here that n
Timothy Lanfear writes:
> Bug appears in 2.19.46 and .47. Ubuntu 16.04, 64-bit.
>
> The first line provokes a core dump. The second line is perhaps the
> right syntax for this construction and works fine, but I'm reporting
> in case there is something here that needs investigating.
>
> \version "
Bug appears in 2.19.46 and .47. Ubuntu 16.04, 64-bit.
The first line provokes a core dump. The second line is perhaps the
right syntax for this construction and works fine, but I'm reporting in
case there is something here that needs investigating.
\version "2.19.46"
{
2\fermata ~ b'2 % c
11 matches
Mail list logo
