[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Segfault 2.13.47
From: |
Reinhold Kainhofer |
Subject: |
Re: Segfault 2.13.47 |
Date: |
Mon, 31 Jan 2011 16:37:59 +0100 |
User-agent: |
KMail/1.13.5 (Linux/2.6.35-25-generic; KDE/4.6.0; i686; ; ) |
Am Montag, 31. Januar 2011, um 05:01:14 schrieb Jay Anderson:
> It actually occurred somewhere between 2.13.45 and 2.13.46 from what I can
> tell.
Hmm, that's strange, as there was no commit touching the part-combiner between
2.13.45 and 2.13.46...
> More info: I have two parts in the score like this: \partcombine
> \bassoonOne \bassoonTwo where not all of \bassoonTwo is filled in
> (only a few measures at the beginning are there). But isolating the
> score down to just these two parts doesn't result in a segfault. Even
> taking out an unrelated part from the score makes the segfault go
> away. When I filled in the rest of the part the segfault went away so
> this bug may not be likely to happen under normal circumstances (where
> both part in partcombine are the same length).
>
> I've attached the whole set of files which cause this since I've been
> unable to make a small example. 'score.ly' causes the segfault. Seeing
> the segfault was somewhat disconcerting, but it may not especially
> severe since it is difficult to isolate and it went away when
> completing all the parts.
Unfortunately, I can't reproduce the problem with current master... I tried
running valgrind, but I only get some uninitialized variable warnings for the
usual *mark* functions (I sent a mail to lilypond-devel about these, too).
Cheers,
Reinhold
--
------------------------------------------------------------------
Reinhold Kainhofer, address@hidden, http://reinhold.kainhofer.com/
* Financial & Actuarial Math., Vienna Univ. of Technology, Austria
* http://www.fam.tuwien.ac.at/, DVR: 0005886
* LilyPond, Music typesetting, http://www.lilypond.org
signature.asc
Description: This is a digitally signed message part.