Updates:
Status: Verified
Comment #12 on issue 1382 by PhilEHolmes: Segfault when
setting 'staff-space to 0.0
http://code.google.com/p/lilypond/issues/detail?id=1382
(No comment was entered for this change.)
___
bug-lilypond mailing list
b
Updates:
Status: Fixed
Labels: fixed_2_13_40
Comment #11 on issue 1382 by Carl.D.Sorensen: Segfault when
setting 'staff-space to 0.0
http://code.google.com/p/lilypond/issues/detail?id=1382
Patch is pushed.
11cb980eb068c4d4bcaf20c27f8a0b8eda731c29
___
Updates:
Labels: Patch
Comment #10 on issue 1382 by percival.music.ca: Segfault when
setting 'staff-space to 0.0
http://code.google.com/p/lilypond/issues/detail?id=1382
Carl provided a patch:
http://codereview.appspot.com/3100041/
___
bug-
Comment #9 on issue 1382 by pnorcks: Segfault when setting 'staff-space to
0.0
http://code.google.com/p/lilypond/issues/detail?id=1382
Graham: the snippet does crash with `-dsafe'.
For this particular segfault, I'm still not sure if it is best to manually
override 'staff-space. Perhaps th
Comment #8 on issue 1382 by percival.music.ca: Segfault when
setting 'staff-space to 0.0
http://code.google.com/p/lilypond/issues/detail?id=1382
Well, it's not quite "crashing", but since scheme is turing-complete,
anybody can write a lilypond file which never finishes processing. With
t
Comment #7 on issue 1382 by lemzwerg: Segfault when setting 'staff-space to
0.0
http://code.google.com/p/lilypond/issues/detail?id=1382
Mhmm, I feel very uncomfortable if I know how to reliably crash a
program, ...
It would be a good idea if the `zillion ways' are registered here. BTW,
Comment #6 on issue 1382 by hanwenn: Segfault when setting 'staff-space to
0.0
http://code.google.com/p/lilypond/issues/detail?id=1382
there are a zillion ways to crash lily; this one is not particularly
useful, so prio 0 is going overboard.
__
Comment #5 on issue 1382 by pnorcks: Segfault when setting 'staff-space to
0.0
http://code.google.com/p/lilypond/issues/detail?id=1382
Carl: I agree. I should have time to look at this issue again this weekend.
___
bug-lilypond mailing list
bug-li
Comment #4 on issue 1382 by lemzwerg: Segfault when setting 'staff-space to
0.0
http://code.google.com/p/lilypond/issues/detail?id=1382
Yes, Xavier, it's the right priority. Any input to LilyPond which makes
the program crash is critical.
___
Comment #3 on issue 1382 by Carl.D.Sorensen: Segfault when
setting 'staff-space to 0.0
http://code.google.com/p/lilypond/issues/detail?id=1382
Xavier: Critical, because we ought to have error checking to prevent
segfaults.
Patrick: It seems like we ought to spit out a warning message and
Comment #2 on issue 1382 by x.scheuer: Segfault when setting 'staff-space
to 0.0
http://code.google.com/p/lilypond/issues/detail?id=1382
"Priority-Critical" !?
This is not a "real world" issue: who would set 'staff-space to 0.0 ?!?
Cheers,
Xavier
__
Comment #1 on issue 1382 by pnorcks: Segfault when setting 'staff-space to
0.0
http://code.google.com/p/lilypond/issues/detail?id=1382
This is a divide-by-zero problem. The patch below stops the segfault, but
I'm unsure if this is the solution we want.
diff --git a/lily/staff-symbol-refe
Status: Accepted
Owner:
Labels: Type-Defect Priority-Critical
New issue 1382 by pnorcks: Segfault when setting 'staff-space to 0.0
http://code.google.com/p/lilypond/issues/detail?id=1382
Original report:
http://lists.gnu.org/archive/html/bug-lilypond/2010-10/msg00580.html
The following sni
13 matches
Mail list logo
