Re: Issue 1829 in lilypond: Part_combine_iterator::last_playing_ not initialized

2011-08-22 Thread lilypond
Updates: Status: Verified Comment #2 on issue 1829 by brownian.box: Part_combine_iterator::last_playing_ not initialized http://code.google.com/p/lilypond/issues/detail?id=1829 (No comment was entered for this change.) ___ bug-lilypond

Re: Issue 1829 in lilypond: Part_combine_iterator::last_playing_ not initialized

2011-08-22 Thread lilypond
Updates: Status: Fixed Owner: reinhold...@gmail.com Labels: fixed_2_15_9 Comment #1 on issue 1829 by reinhold...@gmail.com: Part_combine_iterator::last_playing_ not initialized http://code.google.com/p/lilypond/issues/detail?id=1829 Fixed with commit

Re: Part_combine_iterator::last_playing_ not initialized

2011-08-22 Thread Dmytro O. Redchuk
On Sun 21 Aug 2011, 02:44 Dan Eble wrote: > % valgrind reports that a member of Part_combine_iterator is used > % before being initialized. Initializing last_playing_ = SOLO1 in > % the constructor makes the warning go away. > \version "2.14.2" > > \partcombine { s } { s } Added this as 1829: http

Issue 1829 in lilypond: Part_combine_iterator::last_playing_ not initialized

2011-08-22 Thread lilypond
Status: Accepted Owner: Labels: Type-Defect Security Frog New issue 1829 by brownian.box: Part_combine_iterator::last_playing_ not initialized http://code.google.com/p/lilypond/issues/detail?id=1829 Reported by Dan Eble, http://lists.gnu.org/archive/html/bug-lilypond/2011-08/msg00536

Part_combine_iterator::last_playing_ not initialized

2011-08-20 Thread Dan Eble
> I'm not top posting. % valgrind reports that a member of Part_combine_iterator is used % before being initialized. Initializing last_playing_ = SOLO1 in % the constructor makes the warning go away. \version "2.14.2" \partcombine { s } { s } ___ bug