Updates:
Status: Verified
Comment #39 on issue 2335 by gra...@percival-music.ca: 64 bit LilyPond
segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
(No comment was entered for this change.)
___
bug-lilypond mailing list
bug-
Updates:
Status: Fixed
Labels: fixed_2_15_33
Comment #38 on issue 2335 by gra...@percival-music.ca: 64 bit LilyPond
segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
fixed.
___
bug-lilypond mailing list
bug-lilypond
Comment #37 on issue 2335 by d...@gnu.org: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
Any idea whether the fix for issue 2356 causes a difference here?
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://
Comment #36 on issue 2335 by prze...@gmail.com: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
They are not relevant I believe (possibly some articulate bugs).
http://thread.gmane.org/gmane.comp.gnu.lilypond.bugs/33663/focus=33693
And as you've seen already i
Comment #35 on issue 2335 by d...@gnu.org: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
Actually, since the segfault is not being all that helpful right now: What
are the warnings in the versions where they occur? It might be easier to
rein in an area f
lilyp...@googlecode.com writes:
> Comment #31 on issue 2335 by prze...@gmail.com: 64 bit LilyPond segfaults
> http://code.google.com/p/lilypond/issues/detail?id=2335
>
> Adding empty lines does not help (I tried it almost immediately at the
> beginning, even before reporting the issue).
>
> Just i
Updates:
Labels: -Type-Critical Type-Crash
Comment #34 on issue 2335 by philehol...@gmail.com: 64 bit LilyPond
segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
Keeps head down...
The reason I didn't mark this as a critical regression is that I spent some
time looki
Comment #33 on issue 2335 by prze...@gmail.com: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
Ok. I'll maybe try to touch it next weekend, but I cannot promise anything
now.
___
bug-lilypond mailing list
bug-li
Comment #32 on issue 2335 by gra...@percival-music.ca: 64 bit LilyPond
segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
Graham, would it be possible to build LilyPond in the same way as
provided binaries are built, but w/o stripping debug symbols?
No. Or rather: it is ce
Comment #31 on issue 2335 by prze...@gmail.com: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
Adding empty lines does not help (I tried it almost immediately at the
beginning, even before reporting the issue).
Just in case someone overlooked it, I repeat w
Comment #30 on issue 2335 by gra...@percival-music.ca: 64 bit LilyPond
segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
valgrind reports a ton of memory invalid reads... but it also reports a ton
of jumps depending on uninitialized variables. I mean, not just running
val
Comment #29 on issue 2335 by d...@gnu.org: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
#(gc) does not add music events in a music list. So unless it is an input
alignment problem (does adding empty lines change anything?), this is a
rather sure pointer
Comment #28 on issue 2335 by prze...@gmail.com: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
Beside the line mentioned by Graham (damn, I overlooked it), \unfoldRepeats
can be removed too.
David, the problem is that changing this file in almost any way ma
Comment #27 on issue 2335 by d...@gnu.org: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
It's likely that if you crank some knob concerning garbage collection that
things will be totally different. Unfortunately I see no such knob. Try
putting some #(gc)
Comment #26 on issue 2335 by gra...@percival-music.ca: 64 bit LilyPond
segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
Mike: the bug reporter claimed that he had a tiny example. I called him on
it; he produced another two versions. His final version still looks
large-i
Comment #25 on issue 2335 by mts...@gmail.com: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
This is what I meant. I can make LilyPond segfault w/ many a Scheme hack.
Any function that uses unsmob_spanner, for example, will likely segfault if
a grob is p
Comment #24 on issue 2335 by d...@gnu.org: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
From Scheme, you can't really do much of hacking smobs and memory
management. It is likely that anything you can do to make the problem
disappear is more related to g
Comment #23 on issue 2335 by mts...@gmail.com: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
The articulate script has tons of (cool) hacks, many of which may be doing
funny things w/ smobs and memory management. I'd recommend going into the
script and co
Comment #22 on issue 2335 by prze...@gmail.com: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
Sorry for off-topic comment, but I feel I have to add this.
This piece is a fragment of my WIP work (well, lately not in progress at
all) that I named early "Tempt
Comment #21 on issue 2335 by d...@gnu.org: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
Even "useless" lines produce music events. As long as it is not purely in
the grob juggling part that the problem is occuring, that is not all that
spectacular.
__
Comment #20 on issue 2335 by prze...@gmail.com: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
I never thought I would say it, but I regret that I was not lying (and the
input works flawlessly in 2.14.2, obviously).
$ /home/przemoc/lilypond/2.14.02/usr/bin/
Comment #19 on issue 2335 by gra...@percival-music.ca: 64 bit LilyPond
segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
holy mao. I owe you an apology, przemoc.
I have verified that commenting out "useless" lines will eliminate the
segfault. strange-bug-strip-3.ly segfau
Comment #18 on issue 2335 by gra...@percival-music.ca: 64 bit LilyPond
segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
It segfaults on my machine too, so don't feel that it's you personally
guilty (unless you were lying about it working on 2.14.2). I'm not going
to chec
Comment #17 on issue 2335 by d...@gnu.org: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
I am afraid that particularly with a stable release, people tend to use the
provided binaries.
I hate this cross compilation multiplatform business.
Comment #16 on issue 2335 by prze...@gmail.com: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
As it happens extremely rare, only on Linux 64-bit and only on provided
builds, maybe it doesn't need to be marked as critical? I mean, it could
needlessly delay
Comment #15 on issue 2335 by prze...@gmail.com: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
Nope.
$ lilypond -ddebug-gc ./strange-bug-strip-3.ly
GNU LilyPond 2.15.30
Processing `./strange-bug-strip-3.ly'
Parsing...
Interpreting music... [8][16]Segmentation
Comment #14 on issue 2335 by prze...@gmail.com: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
I missed ties and slurs, they can be removed, but beside that, yes, almost
anything (I may missed something) changed here make segfault gone (and
definitely remov
Comment #13 on issue 2335 by d...@gnu.org: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
Any differences in behavior or output with -ddebug-gc ?
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.
Comment #12 on issue 2335 by gra...@percival-music.ca: 64 bit LilyPond
segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
... seriously? You absolutely *must* have the \time signature? Remove a
single tie ~ will make it work? Removing the left or right hand will make
it
Comment #11 on issue 2335 by prze...@gmail.com: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
Here is possibly the limit of my squeezing. Removing _any_ non empty line
here makes segfault disappear. Heck, change first 'dis' to 'd' and it
works. Magic!
At
Comment #10 on issue 2335 by prze...@gmail.com: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
I understand you, but it may be a bug that just doesn't manifest when the
code is short. I'll try to simplify it as much as I can preserving the
segfault.
Comment #9 on issue 2335 by gra...@percival-music.ca: 64 bit LilyPond
segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
@comment 4: guidelines for making a Tiny example are here:
http://lilypond.org/tiny-examples.html
if you can't be bothered to follow them, then I can't be b
Comment #8 on issue 2335 by prze...@gmail.com: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
As stated in the mails and in this issue description, problem regards Linux
64-bit builds linked from LilyPond site. My own build doesn't segfault.
__
Comment #7 on issue 2335 by d...@gnu.org: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
That's basically useless: looks like you have binaries without debug
symbols. Do have a way to compile the code yourself? If that were
possible, one could at least tr
Comment #6 on issue 2335 by prze...@gmail.com: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
My bad, there is some backtrace available after all:
#0 0x00618a31 in ?? ()
#1 0x0049321d in ?? ()
#2 0x0048b977 in ?? ()
#3 0x00
Comment #5 on issue 2335 by prze...@gmail.com: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
David, my first mail had result from gdb, but it's useless:
Program received signal SIGSEGV, Segmentation fault.
0x00618a31 in ?? ()
I provided ltrace dump:
h
Comment #4 on issue 2335 by prze...@gmail.com: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
I would simplify it if I knew how to do it preserving the segfault. :)
Summary of tests performed using 64-bit LilyPonds in Debian Wheezy x64 (as
it should be here
Comment #3 on issue 2335 by d...@gnu.org: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
Can you crash it in the debugger? If that does not work, can you switch on
core dumps (ulimit -c unlimited) and then use the debugger to give a
backtrace?
_
Comment #2 on issue 2335 by gra...@percival-music.ca: 64 bit LilyPond
segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
woah, that ly is huge! I would have rejected it for not having a Tiny
example.
Could you reduce that to a Tiny example? I particular want to know about
Updates:
Labels: -Type-Crash Type-Critical
Comment #1 on issue 2335 by gra...@percival-music.ca: 64 bit LilyPond
segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
according to his information about the history, this did not crash in
2.14.2.
___
Status: Accepted
Owner:
Labels: Type-Crash OpSys-Linux
New issue 2335 by philehol...@gmail.com: 64 bit LilyPond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2335
Reported by Przemysław 'Przemoc' Pawełczyk
With the attached LilyPond source, lilypond downloaded 64 bit binarie
41 matches
Mail list logo
