Re: Core dump with combination of tie, fermata and some pitches

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

Re: Core dump with combination of tie, fermata and some pitches

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

Re: Core dump with combination of tie, fermata and some pitches

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/

Re: Core dump with combination of tie, fermata and some pitches

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

Re: Core dump with combination of tie, fermata and some pitches

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

Re: Core dump with combination of tie, fermata and some pitches

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

Re: Core dump with combination of tie, fermata and some pitches

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

Re: Core dump with combination of tie, fermata and some pitches

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

Re: Core dump with combination of tie, fermata and some pitches

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 "

Core dump with combination of tie, fermata and some pitches

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

Re: Bracketized key signature: \key c \major causes a core dump

Thomas Morley writes: > 2016-09-02 13:28 GMT+02:00 David Kastrup : >> Thomas Morley writes: >> >>> Below an in-file fix curing the symptoms. >>> >>> David, apart from fixing the internals, does it make sense to prepare >>> a patch for bracketify-stencil at the lines of: >>> >>> \version "2.19.47

Re: Bracketized key signature: \key c \major causes a core dump

2016-09-02 13:28 GMT+02:00 David Kastrup : > Thomas Morley writes: > >> Below an in-file fix curing the symptoms. >> >> David, apart from fixing the internals, does it make sense to prepare >> a patch for bracketify-stencil at the lines of: >> >> \version "2.19.47" >> >> %% not public, c/p from li

Re: Bracketized key signature: \key c \major causes a core dump

Thomas Morley writes: > Below an in-file fix curing the symptoms. > > David, apart from fixing the internals, does it make sense to prepare > a patch for bracketify-stencil at the lines of: > > \version "2.19.47" > > %% not public, c/p from lily-library.scm > #(define (other-axis a) > (remainde

Re: Bracketized key signature: \key c \major causes a core dump

Thanks, I will try this out ASAP! Rutger On 09/02/2016 11:52 AM, Thomas Morley wrote: 2016-09-02 11:44 GMT+02:00 Rutger Hofman : I guess I have been too zealous in minimizing my example that still produces a core dump. My original example is to have a bracketed keysig and later a bracketed key

Re: Simultaneous notes yield "programming error"

2016-09-02 9:59 GMT+02:00 Timothy Lanfear : > See the similar report by me to this list on 6 August and Harm's reply. > > Timothy Lanfear I've redone testing with Joel's file and a snapshot form latest master. No error or warning. Cheers, Harm ___ bu

Re: Bracketized key signature: \key c \major causes a core dump

2016-09-02 11:44 GMT+02:00 Rutger Hofman : > I guess I have been too zealous in minimizing my example that still produces > a core dump. My original example is to have a bracketed keysig and later a > bracketed key change to c \major (i.e. key cancellation), like so: > > { > \override Staff.KeySi

Re: Bracketized key signature: \key c \major causes a core dump

I guess I have been too zealous in minimizing my example that still produces a core dump. My original example is to have a bracketed keysig and later a bracketed key change to c \major (i.e. key cancellation), like so: { \override Staff.KeySignature.stencil = #(lambda (grob) (bracketify-ste

Re: Bracketized key signature: \key c \major causes a core dump

2016-09-02 10:07 GMT+02:00 David Kastrup : > Rutger Hofman writes: > >> Good morning list, >> >> I use the snippet http://lsr.di.unimi.it/LSR/Snippet?id=647 to get a >> key signature in brackets. This works fine for \key other than c >> \major, but if I specify c \major I get a core dump: >> >> Pr

Re: Bracketized key signature: \key c \major causes a core dump

Rutger Hofman writes: > Good morning list, > > I use the snippet http://lsr.di.unimi.it/LSR/Snippet?id=647 to get a > key signature in brackets. This works fine for \key other than c > \major, but if I specify c \major I get a core dump: > > Preprocessing graphical objects...lilypond: > /home/gub

Re: Simultaneous notes yield "programming error"

Simon Albrecht writes: > Hi Joel, > > thanks for the report. > > On the user list, I may have exaggerated my zeal for minimal > examples. Here on the bug list, however, they are more strictly > required, so the bass clef and bar checks (which I believe are > certainly unrelated with the bug – can

Re: Simultaneous notes yield "programming error"

See the similar report by me to this list on 6 August and Harm's reply. Timothy Lanfear > On 2 Sep 2016, at 08:38, Simon Albrecht wrote: > > Hi Joel, > > thanks for the report. > > On the user list, I may have exaggerated my zeal for minimal examples. Here > on the bug list, however, they a

Re: Bracketized key signature: \key c \major causes a core dump

Thanks Rutger, this has been raised as issue 4963 . Best, Simon On 02.09.2016 08:41, Rutger Hofman wrote: Good morning list, I use the snippet http://lsr.di.unimi.it/LSR/Snippet?id=647 to get a key signature in brackets. This works fine

Re: Simultaneous notes yield "programming error"

Hi Joel, thanks for the report. On the user list, I may have exaggerated my zeal for minimal examples. Here on the bug list, however, they are more strictly required, so the bass clef and bar checks (which I believe are certainly unrelated with the bug – can’t test on Linux) could’ve been lef