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.
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
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.)
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
Comment #11 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 am attaching the valgrind log file for a previous bombout involving a
null pointer (few weeks ago). I have not been
Comment #12 on issue 1732 by reinhold...@gmail.com: occasional segfault
when compiling input/regression/midi/key-initial.ly
http://code.google.com/p/lilypond/issues/detail?id=1732
You might want to add the suppressions from the attached file, which
filters practically all spurious warnings
lilyp...@googlecode.com writes:
Comment #12 on issue 1732 by reinhold...@gmail.com: occasional
segfault when compiling input/regression/midi/key-initial.ly
http://code.google.com/p/lilypond/issues/detail?id=1732
You might want to add the suppressions from the attached file, which
filters
Comment #13 on issue 1732 by reinhold...@gmail.com: occasional segfault
when compiling input/regression/midi/key-initial.ly
http://code.google.com/p/lilypond/issues/detail?id=1732
Looking through the code, it appears as follows to me:
-) Grob::internal_set_property calls Grob::is_live (),
On Aug 23, 2011, at 2:38 PM, lilyp...@googlecode.com wrote:
Comment #13 on issue 1732 by reinhold...@gmail.com: occasional segfault when
compiling input/regression/midi/key-initial.ly
http://code.google.com/p/lilypond/issues/detail?id=1732
Looking through the code, it appears as follows
Mike Solomon mike...@ufl.edu writes:
On Aug 23, 2011, at 2:38 PM, lilyp...@googlecode.com wrote:
Comment #13 on issue 1732 by reinhold...@gmail.com: occasional
segfault when compiling input/regression/midi/key-initial.ly
http://code.google.com/p/lilypond/issues/detail?id=1732
Looking
Comment #14 on issue 1732 by reinhold...@gmail.com: occasional segfault
when compiling input/regression/midi/key-initial.ly
http://code.google.com/p/lilypond/issues/detail?id=1732
Backtrace from David for tablature-string-tunings.ly:
Program received signal SIGSEGV, Segmentation fault.
On Aug 23, 2011, at 6:02 PM, lilyp...@googlecode.com wrote:
Okay, I revise my comment 13. It looks different. With that backtrace (notice
this=0x12 in Grob::internal_set_property!) it rather looks like the
Engraver_group::acknowledge_grobs has a Grob_info entry in the
announce_infos_
Mike Solomon mike...@ufl.edu writes:
On Aug 23, 2011, at 6:02 PM, lilyp...@googlecode.com wrote:
Okay, I revise my comment 13. It looks different. With that
backtrace (notice this=0x12 in Grob::internal_set_property!) it
rather looks like the Engraver_group::acknowledge_grobs has a
Comment #15 on issue 1732 by fedel...@gmail.com: occasional segfault when
compiling input/regression/midi/key-initial.ly
http://code.google.com/p/lilypond/issues/detail?id=1732
I'm on Debian Wheezy (32-bit).
See the attached log.
Attachments:
valgrind_key-initial.log 78.2 KB
Comment #9 on issue 1732 by fedel...@gmail.com: occasional segfault when
compiling input/regression/midi/key-initial.ly
http://code.google.com/p/lilypond/issues/detail?id=1732
Currently I can't reproduce the error in the lilypond/translation branch:
b3b16f007ed56ccac625596866d2ff8c081b4a5b
Comment #10 on issue 1732 by reinhold...@gmail.com: occasional segfault
when compiling input/regression/midi/key-initial.ly
http://code.google.com/p/lilypond/issues/detail?id=1732
Which Operating system and which platform (32- or 64-bit) is this?
Do you have valgrind available? if so, could
Updates:
Labels: -Priority-Critical Priority-High
Comment #8 on issue 1732 by percival.music.ca: occasional segfault when
compiling input/regression/midi/key-initial.ly
http://code.google.com/p/lilypond/issues/detail?id=1732
given the difficulty in reproducing this problem, I'm
Comment #6 on issue 1732 by reinhold...@gmail.com: occasional segfault when
compiling input/regression/midi/key-initial.ly
http://code.google.com/p/lilypond/issues/detail?id=1732
The error message throw from within critical section. indicates that this
is a problem somewhere in threaded
Comment #5 on issue 1732 by joenee...@gmail.com: occasional segfault when
compiling input/regression/midi/key-initial.ly
http://code.google.com/p/lilypond/issues/detail?id=1732
Ok, Frederico says it doesn't help. But it fixes a segfault for me, so I'll
push it anyway...
Comment #2 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
I've set up a shell script to run this 100 times, and it ran successfully
all 100 times with my shell script.
Comment #3 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
I'm at 200 runs with no error.
For the record, here's the rest of the output when it succeeds:
Preprocessing
Comment #4 on issue 1732 by joenee...@gmail.com: occasional segfault when
compiling input/regression/midi/key-initial.ly
http://code.google.com/p/lilypond/issues/detail?id=1732
Does the attached patch help?
Attachments:
0001-Fix-a-segfault-caused-by-improper-initialization-of-.patch
Status: Accepted
Owner:
Labels: Type-Defect Priority-Critical
New issue 1732 by percival.music.ca: occasional segfault when compiling
input/regression/midi/key-initial.ly
http://code.google.com/p/lilypond/issues/detail?id=1732
Here's the verbose output of the command (which fails
Comment #1 on issue 1732 by brownian.box: occasional segfault when
compiling input/regression/midi/key-initial.ly
http://code.google.com/p/lilypond/issues/detail?id=1732
http://lists.gnu.org/archive/html/bug-lilypond/2011-07/msg00027.html
24 matches
Mail list logo