Re: Somewhat random segfault

Le 07/04/2022 à 21:17, Mats Bengtsson a écrit : (If I add the missing \! in the second ending the file no longer triggers the SIGSEGV, but I guess that's more of a coincidence). It actually isn't. This bug was already fixed, see https://gitlab.com/lilypond/lilypond/-/issues/6219 Best,

Somewhat random segfault

Hi, The following example results in a segfault almost every time I process it using the 64bit Linux version of 2.23.7, downloaded from lilypond.org. The log output is GNU LilyPond 2.23.7 (running Guile 2.2) Processing `test1.ly' Parsing... Interpreting music...[

Re: Segfault in MIDI with empty score via skipTypesetting

Hello, On 24/10/2021 14:24, David Kastrup wrote: James writes: if I go up the stack a bit --snip- (gdb) f 3 #3  0x55705abb in audio_item_less (a=0x55d37e90, b=0x55d37df0)     at /home/james/Downloads/git_repos/lilypond-git/lily/midi-walker.cc:54 54    return a->get_co

Re: Segfault in MIDI with empty score via skipTypesetting

James writes: > if I go up the stack a bit > > --snip- > > (gdb) f 3 > #3  0x55705abb in audio_item_less (a=0x55d37e90, > b=0x55d37df0) >     at /home/james/Downloads/git_repos/lilypond-git/lily/midi-walker.cc:54 > 54    return a->get_column ()->when_ < b->get_column ()->when

Re: Segfault in MIDI with empty score via skipTypesetting

hello, On 23/10/2021 23:16, David Kastrup wrote: The following eventually crashes: -*- mode: compilation; default-directory: "/tmp/" -*- Compilation started at Sun Oct 24 00:14:20 lilypond /tmp/bah.ly GNU LilyPond 2.23.5 (running Guile 1.8) Processing `/tmp/bah.ly' Parsing... /tmp/bah.ly:1: w

Segfault in MIDI with empty score via skipTypesetting

The following eventually crashes: \version "2.23.5" \score { { \set Score.skipTypesetting = ##t c1 } \midi { } }-*- mode: compilation; default-directory: "/tmp/" -*- Compilation started at Sun Oct 24 00:14:20 lilypond /tmp/bah.ly GNU LilyPond 2.23.5 (running Guile 1.8) Processing

RE: Segfault when using specific symbol combination

Thank you for your quick response! I tried Lilypond 2.20 now on Windows and Linux and the segfault disappeared. Sorry for the false alarm. I did not try 2.20 in the first place, because I did not find any bug report and thought that the error appears under such specific circumstances that it

Re: Segfault when using specific symbol combination

Mathias Bockwoldt writes: > Dear Lilypond team, > > I found a symbol combination that triggers a segfault in Lilypond > 2.18.2 on Linux (Linux subsystem for Windows 10). I did not have the > chance to reproduce on other machines or with other versions. > I tried looking

Re: Segfault when using specific symbol combination

Il giorno ven 6 mar 2020 alle 11:38, Mathias Bockwoldt ha scritto: Dear Lilypond team, I found a symbol combination that triggers a segfault in Lilypond 2.18.2 on Linux (Linux subsystem for Windows 10). I did not have the chance to reproduce on other machines or with other versions. I

Segfault when using specific symbol combination

Dear Lilypond team, I found a symbol combination that triggers a segfault in Lilypond 2.18.2 on Linux (Linux subsystem for Windows 10). I did not have the chance to reproduce on other machines or with other versions. I tried looking for the bug in the database and I am 98% sure that it is not

Re: Segfault with slur over tie 2.18.2

the LilyPond website? Next, in the event it's > more than just `lilypond foo.ly`, would you please provide the complete > command-line you are running? Lastly, what program output do you get > with the segfault? > > -- Aaron Hill >

Re: Segfault with slur over tie 2.18.2

it's more than just `lilypond foo.ly`, would you please provide the complete command-line you are running? Lastly, what program output do you get with the segfault? -- Aaron Hill ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists

Re: Segfault with slur over tie 2.18.2

On Sun, 01 Sep 2019 16:45:16 -0700, Aaron Hill wrote: > On 2019-09-01 3:44 pm, Jason Miller wrote: > > See attached example. This was originally encountered on nixos, but I > > confirmed it also happens on Ubuntu. > > Is this a valid case? The code as attached appears to be malformed: Sorry, I

Re: Segfault with slur over tie 2.18.2

On 2019-09-01 3:44 pm, Jason Miller wrote: See attached example. This was originally encountered on nixos, but I confirmed it also happens on Ubuntu. Is this a valid case? The code as attached appears to be malformed: GNU LilyPond 2.19.83 Processing `foo.ly' Parsing... foo.ly:6:3: error

Segfault with slur over tie 2.18.2

See attached example. This was originally encountered on nixos, but I confirmed it also happens on Ubuntu. \version "2.18.2" \new Staff { f8( e~ e2.) | } >> ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/

Re: programming error/segfault while omitting Fingering.stencil with fingeringOrientations set 'left

Hi, Harm - Thanks. This has been entered as issue #5476. All the best, Ralph On Mon, Jan 21, 2019 at 4:03 PM Thomas Morley wrote: > > Hi, > > the following code is problematic > > { > \set fingeringOrientations = #'(left) > \override Fingering #'stencil = ##f > %% chord needs two elements

programming error/segfault while omitting Fingering.stencil with fingeringOrientations set 'left

Hi, the following code is problematic { \set fingeringOrientations = #'(left) \override Fingering #'stencil = ##f %% chord needs two elements to trigger the bug } Versions 2.12.3 up to 2.16.2 print correctly, without error Versions 2.18.2 up to 2.19.82 print correctly, but return: progr

Re: Segfault with midi and \new StaffGroup

Hello again, this is now <https://sourceforge.net/p/testlilyissues/issues/5234/>. Best, Simon On 07.11.2017 23:49, Simon Albrecht wrote: Hello everybody, this code generates a segfault using 2.19.80 (Ubuntu 16.04, 64-bit): \version "2.19.80" \score {   \new Staff

Segfault with midi and \new StaffGroup

Hello everybody, this code generates a segfault using 2.19.80 (Ubuntu 16.04, 64-bit): \version "2.19.80" \score {   \new StaffGroup {}   \midi {} } $ lilypond debug.ly GNU LilyPond 2.19.80 Processing `debug.ly' Parsing... Interpreting music... warning: no music found in score

Segfault for balloonGrobText on OttavaBracket

Hi, the following code produces a segmentation violation (if that's the same as "Speicherzugriffsfehler") using 2.18.2 or 2.19.50. The combination of \ottava and \balloonGrobText is required to cause the failure. \version "2.19.50" \new Staff \with { \consists "Balloon_engraver" } \new Voice {

Re: segfault in 2.19.45

> Hi, Fedora lilypond maintainer. We've actually got our 2.19.45 patched, but > the update was superceded by 2.19.46. If you do sudo dnf update lilypond* > --enablerepo=updates-testing you should get it. Many thanks; this fixed it! ___ bug-lilypond ma

Re: segfault in 2.19.45

On Fri, Jul 29, 2016 at 12:32 PM, Kevin Barry wrote: > Thank you for taking the time to test it. I'm using the package in > Fedora's repo, so I suppose I should take it up with them? I'm not > sure how to troubleshoot further. Reinstalling didn't help. > > Kevin > > __

Re: segfault in 2.19.45

At 18:32 on 29 Jul 2016, Kevin Barry wrote: >Thank you for taking the time to test it. I'm using the package in >Fedora's repo, so I suppose I should take it up with them? I'm not >sure how to troubleshoot further. Reinstalling didn't help. http://git.savannah.gnu.org/cgit/lilypond.git/commit/?id=

Re: segfault in 2.19.45

Thank you for taking the time to test it. I'm using the package in Fedora's repo, so I suppose I should take it up with them? I'm not sure how to troubleshoot further. Reinstalling didn't help. Kevin ___ bug-lilypond mailing list bug-lilypond@gnu.org ht

Re: segfault in 2.19.45

ons should segfault). There must be some kind of problem caused by the slur and tie ending in the same place. \version "2.19.45" { a( b~ b) } Starting lilypond 2.19.45 [test.ly]... Processing `test.ly' Parsing... Interpreting music... Preprocessing graphical objects... Finding the ideal n

Re: segfault in 2.19.45

WE follows (compiling with no options should segfault). There must be some kind of problem caused by the slur and tie ending in the same place. \version "2.19.45" { a( b~ b) } Starting lilypond 2.19.45 [test.ly]... Processing `test.ly' Parsing... Interpreting music... Prepro

segfault in 2.19.45

Apologies if this is fixed in 2.19.46 It worked in previous versions of 2.19 (I'm not sure when it broke cause it's not from something i worked on too recently). I am on Linux 64-bit (Fedora). A MWE follows (compiling with no options should segfault). There must be some kind of problem

Segfault when using \lookup?

Hello all, I am trying to insert a few unencoded (but named) glyphs from an OpenType font (i.e., glyphs not associated with a codepoint in the cmap table). I haven't yet figured out if it's possible — if you know how, please tell me! I ran lilypond 2.19.31 on the following example while investiga

Re: French beams over rests cause segfault

"Jean Menezes da Rocha" wrote in message news:CALRb6h+_gWgeU1=6wruogawua7hsddya8zx0vsy97is7tci...@mail.gmail.com... I have seen, according to this [1], that Kastrup created a patch to address this issue. Is there any way I can apply this patch by now,

Re: French beams over rests cause segfault

#63 0x779133f0 in scm_c_with_continuation_barrier () from >> /usr/lib/libguile.so.17 >> No symbol table info available. >> #64 0x77977956 in scm_i_with_guile_and_parent () from >> /usr/lib/libguile.so.17 >> No symbol table info available.

Re: French beams over rests cause segfault

Thanks Simon, I am gonna take a risk and try to compile a patched version using the .diff file. Best regards! On Thu, Nov 5, 2015 at 11:52 AM, Simon Albrecht wrote: > On 05.11.2015 14:45, Jean Menezes da Rocha wrote: > >> I have seen, according to this

Re: French beams over rests cause segfault

On 05.11.2015 14:45, Jean Menezes da Rocha wrote: I have seen, according to this [1], that Kastrup created a patch to address this issue. Is there any way I can apply this patch by now, or should I wait for a new development release containing a defin

Re: French beams over rests cause segfault

stopped by a segmentation fault. I can confirm that from 2.16 onward, so I created <https://sourceforge.net/p/testlilyissues/issues/4653/>. this example: \version "2.19.30" \relative c'' { \ove

Re: French beams over rests cause segfault

eated <https://sourceforge.net/p/testlilyissues/issues/4653/>. this example: \version "2.19.30" \relative c'' { \override Stem.french-beaming = ##t c16[ d e r] } always produces a segfault, Could you please provide a backtrace for this minimal

French beams over rests cause segfault

nch-beaming = ##t c16[ d e r] } always produces a segfault, while \version "2.19.30" \relative c'' { \override Stem.french-beaming = ##t c16[ d e f] } does not. Starting the group with a rest won't be harmful, either. Only rests ending a group of 'fre

Re: Slur_proto_engraver segfault

"Phil Holmes" writes: > - Original Message - > From: "David Kastrup" > >> Phil, this is absolutely serious stuff, likely causing crashes for large >> scores on most platforms. Too bad we did not catch this (no idea why) >> in time. >> >> I wonder whether we have a chance to actually _r

Re: Slur_proto_engraver segfault

- Original Message - From: "David Kastrup" Phil, this is absolutely serious stuff, likely causing crashes for large scores on most platforms. Too bad we did not catch this (no idea why) in time. I wonder whether we have a chance to actually _retract_ 2.19.29, but short of that, we re

Re: Slur_proto_engraver segfault

David Kastrup writes: > Dan Eble writes: > >> Forgive me for being brief, but I thought I should at least mention >> this in case someone would like to approach it with code review: >> >> Thread 0 Crashed:: Dispatch queue: com.apple.main-thread >> 0 lilypond 0x001f35ff Slur_proto_engraver::deriv

Re: Slur_proto_engraver segfault

Dan Eble writes: > Forgive me for being brief, but I thought I should at least mention > this in case someone would like to approach it with code review: > > Thread 0 Crashed:: Dispatch queue: com.apple.main-thread > 0 lilypond 0x001f35ff Slur_proto_engraver::derived_mark() const + 79 > 1 lilypon

Re: Slur_proto_engraver segfault

> On Oct 23, 2015, at 19:37 , Simon Albrecht wrote: > > Perhaps it’s immediately understandable by someone more technically apt than > me, but I can’t see what you actually did here, when the error occurred. Did > you compile an .ly file? Could you share a minimal example? I don’t have time.

Re: Slur_proto_engraver segfault

Hello Dan, On 24.10.2015 00:54, Dan Eble wrote: Forgive me for being brief, but I thought I should at least mention this in case someone would like to approach it with code review: Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 lilypond0x001f35ff Slur

Slur_proto_engraver segfault

Forgive me for being brief, but I thought I should at least mention this in case someone would like to approach it with code review: Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 lilypond0x001f35ff Slur_proto_engraver::derived_mark() const + 79 1 lily

Re: Segfault with voice and empty music

ix, putting synchronized music and independent non-synchronized music of different length at the same level will likely cause trouble. A segfault, however, is more trouble than permissible. > (Duh: The reason that I'm generating empty music is that I'm > conditionally inserting other lyri

Segfault with voice and empty music

Hi folks I've noticed the following problem in 2.19.16 after updating from 2.19.11. When the code below compiles I get the error "warning: cannot find Voice `refrain" and then the compilation segfaults. If I comment out the line marked "NOT OK" then the compilation and the output are fine.

Re: Segfault from unusual time signatures

Dan Eble gmail.com> writes: > > >>> % This input caused a segfault on OS X Yosemite with Lilypond 2.19.15. > > >>> \version "2.19.0" > > >>> \new Staff { > > >>> \relative d' { > > >>> \ti

Re: Segfault from unusual time signatures

Urs Liska googlemail.com> writes: > > Am 26.10.2014 21:39, schrieb David Kastrup: > > Urs Liska googlemail.com> writes: > > > >> Am 26.10.2014 21:19, schrieb Dan Eble: > >>> % This input caused a segfault on OS X Yosemite with Lilypond 2.19

Re: Segfault from unusual time signatures

Am 26.10.2014 21:39, schrieb David Kastrup: Urs Liska writes: Am 26.10.2014 21:19, schrieb Dan Eble: % This input caused a segfault on OS X Yosemite with Lilypond 2.19.15. \version "2.19.0" \new Staff { \relative d' { \time 8/1024 d128 | \time 9/1 d1

Re: Segfault from unusual time signatures

Urs Liska writes: > Am 26.10.2014 21:19, schrieb Dan Eble: >> % This input caused a segfault on OS X Yosemite with Lilypond 2.19.15. >> \version "2.19.0" >> \new Staff { >>\relative d' { >> \time 8/1024 d128 | >> \time 9/1 d

Re: Segfault from unusual time signatures

Am 26.10.2014 21:19, schrieb Dan Eble: % This input caused a segfault on OS X Yosemite with Lilypond 2.19.15. \version "2.19.0" \new Staff { \relative d' { \time 8/1024 d128 | \time 9/1 d1 } } Compiled without problem on a build from current master (Deb

Segfault from unusual time signatures

% This input caused a segfault on OS X Yosemite with Lilypond 2.19.15. \version "2.19.0" \new Staff { \relative d' { \time 8/1024 d128 | \time 9/1 d1 } } ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.

Re: Segfault

On Oct 11, 2013, at 8:18 PM, Colin Campbell wrote: > On 13-10-11 06:55 AM, Mike Solomon wrote: >> \version "2.17.26" >> >> \score { >> \new Staff {} >> \midi {} >> } >> >> Ultra-minimalist composers everywhere are completely blocked until someone >> fixes this. >> >> Cheers, >> MS >> ___

Re: Segfault

On 13-10-11 06:55 AM, Mike Solomon wrote: \version "2.17.26" \score { \new Staff {} \midi {} } Ultra-minimalist composers everywhere are completely blocked until someone fixes this. Cheers, MS ___ bug-lilypond mailing list bug-lilypond@gnu.org

Re: Segfault

Mike Solomon writes: > \version "2.17.26" > > \score { > \new Staff {} > \midi {} > } > > Ultra-minimalist composers everywhere are completely blocked until > someone fixes this. http://code.google.com/p/lilypond/issues/detail?id=2392> I prefer not doing the comparably simple paste-over-the

Segfault

\version "2.17.26" \score { \new Staff {} \midi {} } Ultra-minimalist composers everywhere are completely blocked until someone fixes this. Cheers, MS ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-li

Re: segfault with 2.17.12

Hello, 2013/4/3 Jan Nieuwenhuizen > I made this typo > > \layout { > music = { } > { \music } > > and Lily segfaults on me. > Thank you for the report, this has been added as http://code.google.com/p/lilypond/issues/detail?id=3323 Marek bug squad member _

Re: segfault with 2.17.12

Jan Nieuwenhuizen writes: > Hi, > > I made this typo > > \layout { > music = { } > { \music } > > and Lily segfaults on me. What happens is that the lexer encounters an unexpected EOF. It cleans up the lexer state and delivers EOF to the parser. However, EOF to the parser does not

segfault with 2.17.12

Hi, I made this typo \layout { music = { } { \music } and Lily segfaults on me. Greetings, Jan -- Jan Nieuwenhuizen | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl ___ bug-lil

Re: Issue 2393 in lilypond: Segfault in connection with \markuplist

Comment #6 on issue 2393 by pkx1...@gmail.com: Segfault in connection with \markuplist http://code.google.com/p/lilypond/issues/detail?id=2393 Also on 2.12.3 on Windows crashes too. ___ bug-lilypond mailing list bug-lilypond@gnu.org https

Re: Issue 2393 in lilypond: Segfault in connection with \markuplist

Comment #5 on issue 2393 by d...@gnu.org: Segfault in connection with \markuplist http://code.google.com/p/lilypond/issues/detail?id=2393 So this is not a regression. That's good news for 2.16 release planning. Still needs to get investigated. #(display #{ \markuplist \bold { \wor

Re: Issue 2393 in lilypond: Segfault in connection with \markuplist

Comment #4 on issue 2393 by thomasmo...@gmail.com: Segfault in connection with \markuplist http://code.google.com/p/lilypond/issues/detail?id=2393 Should be: I'm on Linux 64-bit Ubuntu 10.04 ___ bug-lilypond mailing list bug-lilypond@gn

Re: Issue 2393 in lilypond: Segfault in connection with \markuplist

Comment #3 on issue 2393 by thomasmo...@gmail.com: Segfault in connection with \markuplist http://code.google.com/p/lilypond/issues/detail?id=2393 2.12.3 crashes,too I'm on Linux 64-bit 10.04 Compiled with Frescobaldi Code: \version "2.12.3" \markuplines \bold {

Re: Issue 2392 in lilypond: Segfault in connection with \applyContext

Comment #1 on issue 2392 by pkx1...@gmail.com: Segfault in connection with \applyContext http://code.google.com/p/lilypond/issues/detail?id=2392 This also occurs in 2.14.2 (I am using Windows 7) --snip-- Starting lilypond-windows.exe 2.14.2 [Untitled]... Processing `c:/users/jlowe~1.dcs

Re: Issue 2393 in lilypond: Segfault in connection with \markuplist

Comment #2 on issue 2393 by d...@gnu.org: Segfault in connection with \markuplist http://code.google.com/p/lilypond/issues/detail?id=2393 Some. If it also crashes in 2.12, this is not a critical regression. I actually have no idea why something as simple as that would crash (does not

Re: Issue 2393 in lilypond: Segfault in connection with \markuplist

Comment #1 on issue 2393 by pkx1...@gmail.com: Segfault in connection with \markuplist http://code.google.com/p/lilypond/issues/detail?id=2393 2.14.2 crashes (I am using windows 7) --snip-- Starting lilypond-windows.exe 2.14.2 [Untitled]... Processing `c:/users/jlowe~1.dcs/appdata/local

Issue 2393 in lilypond: Segfault in connection with \markuplist

Status: New Owner: Labels: Type-Crash New issue 2393 by d...@gnu.org: Segfault in connection with \markuplist http://code.google.com/p/lilypond/issues/detail?id=2393 Can please somebody check this against being a regression? In earlier versions, \markuplist was called \markuplines

Issue 2392 in lilypond: Segfault in connection with \applyContext

Status: Accepted Owner: Labels: Type-Crash New issue 2392 by d...@gnu.org: Segfault in connection with \applyContext http://code.google.com/p/lilypond/issues/detail?id=2392 \version "2.15.31" \score { { \applyContext #(lambda (x) (display x)) c c c c } \midi { } }

Re: Issue 1997 in lilypond: segfault in tablature-negative-fret.ly

Updates: Status: Verified Comment #37 on issue 1997 by gra...@percival-music.ca: segfault in tablature-negative-fret.ly http://code.google.com/p/lilypond/issues/detail?id=1997 since we can compile GUB, this must be fixed. ___ bug-lilypond

Re: Issue 1997 in lilypond: segfault in tablature-negative-fret.ly

Comment #36 on issue 1997 by philehol...@gmail.com: segfault in tablature-negative-fret.ly http://code.google.com/p/lilypond/issues/detail?id=1997 Needs someone with the correct development environment to verify. ___ bug-lilypond mailing list bug

Re: Segfault 2.15.23 Span_bar_stub_engraver

On Dec 31, 2011, at 10:56 PM, Jay Anderson wrote: > I've been unable to create a good small example so far. When I take > out seemingly unrelated sections it compiles which makes it difficult > to narrow down. Removing the "Span_bar_stub_engraver" from my > PianoStaff f

Segfault 2.15.23 Span_bar_stub_engraver

I've been unable to create a good small example so far. When I take out seemingly unrelated sections it compiles which makes it difficult to narrow down. Removing the "Span_bar_stub_engraver" from my PianoStaff fixes the segfault, but what won't work if I do this? Below i

Re: Issue 1732 in lilypond: occasional segfault when compiling input/regression/midi/key-initial.ly

Updates: Status: Verified Comment #19 on issue 1732 by philehol...@gmail.com: occasional segfault when compiling input/regression/midi/key-initial.ly http://code.google.com/p/lilypond/issues/detail?id=1732 Confirming no recent reports of this as a problem

Re: Issue 1732 in lilypond: occasional segfault when compiling input/regression/midi/key-initial.ly

Updates: Status: Fixed Labels: fixed_2_15_22 Comment #18 on issue 1732 by carl.d.s...@gmail.com: occasional segfault when compiling input/regression/midi/key-initial.ly http://code.google.com/p/lilypond/issues/detail?id=1732 Having had no new report, and having had a fix to

Re: Segfault in 2.13.63

John David Duncan writes: > Hi there, > > I see the following crash in 2.13.63: > > Finding the ideal number of pages... > Fitting music on 1 or 2 pages... > Drawing systems... > Program received signal EXC_BAD_ACCESS, Could not access memory. > Reason: KERN_PROTECTION_FAILURE at address: 0x0

Segfault in 2.13.63

Hi there, I see the following crash in 2.13.63: Finding the ideal number of pages... Fitting music on 1 or 2 pages... Drawing systems... Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_PROTECTION_FAILURE at address: 0x 0x00047e02 in Beam::print () (gdb) bt #0

Re: Issue 1997 in lilypond: segfault in tablature-negative-fret.ly

Comment #35 on issue 1997 by carl.d.s...@gmail.com: segfault in tablature-negative-fret.ly http://code.google.com/p/lilypond/issues/detail?id=1997 Unless I get a report of this problem from a user of the 2.14.2, I don't think we'll backport. Users of stable generally aren&#

Re: Issue 1997 in lilypond: segfault in tablature-negative-fret.ly

Updates: Labels: -Fixed_2_5_21 Fixed_2_15_21 Comment #34 on issue 1997 by d...@gnu.org: segfault in tablature-negative-fret.ly http://code.google.com/p/lilypond/issues/detail?id=1997 Regarding comment 32: pulling into the stable branch might still be warranted. However, it appears

Re: Issue 1997 in lilypond: segfault in tablature-negative-fret.ly

Comment #33 on issue 1997 by d...@gnu.org: segfault in tablature-negative-fret.ly http://code.google.com/p/lilypond/issues/detail?id=1997 Issue 1809 has been merged into this issue. ___ bug-lilypond mailing list bug-lilypond@gnu.org https

Re: Issue 1732 in lilypond: occasional segfault when compiling input/regression/midi/key-initial.ly

Updates: Labels: -Priority-High Comment #17 on issue 1732 by pkx1...@gmail.com: occasional segfault when compiling input/regression/midi/key-initial.ly http://code.google.com/p/lilypond/issues/detail?id=1732 (No comment was entered for this change

Re: Issue 1732 in lilypond: occasional segfault when compiling input/regression/midi/key-initial.ly

Comment #16 on issue 1732 by d...@gnu.org: occasional segfault when compiling input/regression/midi/key-initial.ly http://code.google.com/p/lilypond/issues/detail?id=1732 I consider it likely that this is issue 1997. Can those that experienced the bug here a) report compiler version and

Re: Issue 1997 in lilypond: segfault in tablature-negative-fret.ly

Updates: Status: Fixed Labels: -Patch-push Fixed_2_5_21 Comment #32 on issue 1997 by d...@gnu.org: segfault in tablature-negative-fret.ly http://code.google.com/p/lilypond/issues/detail?id=1997 Pushed as df74defbb64026811fe676309a236fe649116d45 to staging. Verification fo

Re: Issue 1997 in lilypond: segfault in tablature-negative-fret.ly

Updates: Labels: -Patch-countdown Patch-push Comment #31 on issue 1997 by colinpkc...@gmail.com: segfault in tablature-negative-fret.ly http://code.google.com/p/lilypond/issues/detail?id=1997 Counted down to 20111201 ___ bug-lilypond

Re: Issue 1997 in lilypond: segfault in tablature-negative-fret.ly

Updates: Labels: -Patch-new Patch-review Comment #29 on issue 1997 by pkx1...@gmail.com: segfault in tablature-negative-fret.ly http://code.google.com/p/lilypond/issues/detail?id=1997 passes make, make check. Also did a new build using ./autogen --noconfigure then cd build

Re: Issue 1997 in lilypond: segfault in tablature-negative-fret.ly

Comment #27 on issue 1997 by d...@gnu.org: segfault in tablature-negative-fret.ly http://code.google.com/p/lilypond/issues/detail?id=1997#c27 Work around compiler bug, Issue 1997: segfault in tablature-negative-fret.ly http://codereview.appspot.com/5431088

Re: Issue 1997 in lilypond: segfault in tablature-negative-fret.ly

Comment #26 on issue 1997 by carl.d.s...@gmail.com: segfault in tablature-negative-fret.ly http://code.google.com/p/lilypond/issues/detail?id=1997 Looking at Jakub's response to you, it appears that he is in favor of moving to non-buggy compilers, with which I agree. But we

Re: Issue 1997 in lilypond: segfault in tablature-negative-fret.ly

Comment #25 on issue 1997 by d...@gnu.org: segfault in tablature-negative-fret.ly http://code.google.com/p/lilypond/issues/detail?id=1997 If you look at the GCC bug URL given in comment 17, you'll see that Jakub Jelinek has given a self-contained example that is supposed to corr

Re: Issue 1997 in lilypond: segfault in tablature-negative-fret.ly

Updates: Labels: Patch-new Comment #24 on issue 1997 by d...@gnu.org: segfault in tablature-negative-fret.ly http://code.google.com/p/lilypond/issues/detail?id=1997#c24 Work around compiler bug, Issue 1997: segfault in tablature-negative-fret.ly http://codereview.appspot.com/5431088

Re: Issue 1997 in lilypond: segfault in tablature-negative-fret.ly

Comment #23 on issue 1997 by d...@gnu.org: segfault in tablature-negative-fret.ly http://code.google.com/p/lilypond/issues/detail?id=1997 The right option for avoiding the bad optimization would appear to be -fno-optimize-sibling-calls and, frankly, it is actually insane that -fkeep

Re: Issue 1997 in lilypond: segfault in tablature-negative-fret.ly

Updates: Status: Started Cc: gra...@percival-music.ca Comment #22 on issue 1997 by d...@gnu.org: segfault in tablature-negative-fret.ly http://code.google.com/p/lilypond/issues/detail?id=1997 Graham, you have a 64bit target. The code generator for that is entirely

Re: Issue 1997 in lilypond: segfault in tablature-negative-fret.ly

Comment #21 on issue 1997 by gra...@percival-music.ca: segfault in tablature-negative-fret.ly http://code.google.com/p/lilypond/issues/detail?id=1997 hmm, fun and joy here. Brand new mac mini, brand new installation of ubuntu 11.10. make, make doc, make test-baseline, make check is happy

Re: Issue 1997 in lilypond: segfault in tablature-negative-fret.ly

Comment #20 on issue 1997 by carl.d.s...@gmail.com: segfault in tablature-negative-fret.ly http://code.google.com/p/lilypond/issues/detail?id=1997 Can we test for g++-4.6.1, and add the CXXFLAGS=-fkeep-inlinefunctions automatically as part of configure.sh? Thanks for tracking this down

Re: Issue 1997 in lilypond: segfault in tablature-negative-fret.ly

Comment #19 on issue 1997 by d...@gnu.org: segfault in tablature-negative-fret.ly http://code.google.com/p/lilypond/issues/detail?id=1997 At least the following are likely to be broken (since they are quite similar and I get already 2 of them bad). lily/font-size-engraver.cc: gi.grob

Re: Issue 1997 in lilypond: segfault in tablature-negative-fret.ly

Comment #18 on issue 1997 by d...@gnu.org: segfault in tablature-negative-fret.ly http://code.google.com/p/lilypond/issues/detail?id=1997 Ok, forget it. The next segfault is in input/regression/grid-lines.ly. I think we can't do much more than recommend ./autogen.sh CXXFLAGS=-fkeep-i

Re: Issue 1997 in lilypond: segfault in tablature-negative-fret.ly

Comment #17 on issue 1997 by d...@gnu.org: segfault in tablature-negative-fret.ly http://code.google.com/p/lilypond/issues/detail?id=1997 Entered as <http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51323>. I'll add appropriate garbage to the function that will keep g++ from ma

Re: Issue 1997 in lilypond: segfault in tablature-negative-fret.ly

Comment #16 on issue 1997 by d...@gnu.org: segfault in tablature-negative-fret.ly http://code.google.com/p/lilypond/issues/detail?id=1997 Ok, this is a steaming heap of crap. I have tried boiling the original preprocessed source down to something more useful, and I have a 25k file not

Re: Issue 1997 in lilypond: segfault in tablature-negative-fret.ly

Comment #15 on issue 1997 by d...@gnu.org: segfault in tablature-negative-fret.ly http://code.google.com/p/lilypond/issues/detail?id=1997 Bad news. void Tab_staff_symbol_engraver::acknowledge_staff_symbol (Grob_info gi) { int k = scm_ilength (get_property ("stringTunings"));

Re: Issue 1997 in lilypond: segfault in tablature-negative-fret.ly

Comment #14 on issue 1997 by d...@gnu.org: segfault in tablature-negative-fret.ly http://code.google.com/p/lilypond/issues/detail?id=1997 Anyway, I have boiled this down to a minimal example that still crashes. { \set TabStaff.handleNegativeFrets = #'include s } The probl

Re: Issue 1997 in lilypond: segfault in tablature-negative-fret.ly

Comment #13 on issue 1997 by carl.d.s...@gmail.com: segfault in tablature-negative-fret.ly http://code.google.com/p/lilypond/issues/detail?id=1997 David Kastrup tested the patch, and found that it had no effect on the segfault. Thanks, Carl

Re: Issue 1997 in lilypond: segfault in tablature-negative-fret.ly

Comment #12 on issue 1997 by carl.d.s...@gmail.com: segfault in tablature-negative-fret.ly http://code.google.com/p/lilypond/issues/detail?id=1997 Could someone who has observed this segfault try again after testing the patch at http://codereview.appspot.com/5432081/ This is a scheme

Re: Issue 1997 in lilypond: segfault in tablature-negative-fret.ly

Comment #11 on issue 1997 by carl.d.s...@gmail.com: segfault in tablature-negative-fret.ly http://code.google.com/p/lilypond/issues/detail?id=1997 This is probably the same issue as issue 1900, but I'm not going to merge them. I wonder if we've got the problem that Mi

Re: Issue 1997 in lilypond: segfault in tablature-negative-fret.ly

Comment #10 on issue 1997 by d...@gnu.org: segfault in tablature-negative-fret.ly http://code.google.com/p/lilypond/issues/detail?id=1997 For progress (or rather nonprogress) of the "make check" sideissue not really belonging in here, check

  1   2   3   4   >