Am Sunday, 21. August 2011, 05:01:38 schrieb Dan Eble:
> > On 2011-08-20, at 16:00 , Reinhold Kainhofer wrote:
> >> Hmm, do you have any example file where this appears (even if it's not
> >> minimal, for now it's just important that we can reproduce it somehow).
>
> I wonder if this has anything
> On 2011-08-20, at 16:00 , Reinhold Kainhofer wrote:
>
>> So, basically, you are saying that whenever you run "make X" through color,
>> it
>> will crash, but it will not crash in any other cases?
>> Are you sure this is not a problem of color together with make (I had some
>> strange problem
On 2011-08-20, at 16:00 , Reinhold Kainhofer wrote:
> So, basically, you are saying that whenever you run "make X" through color,
> it
> will crash, but it will not crash in any other cases?
> Are you sure this is not a problem of color together with make (I had some
> strange problems that on
Am Saturday, 20. August 2011, 19:29:38 schrieb Dan Eble:
> On 2011-08-18, at 10:11 , Carl Sorensen wrote:
> > On 8/17/11 10:41 PM, "Dan Eble" wrote:
> >> What I have so far is a backtrace:
> >> http://lists.gnu.org/archive/html/lilypond-devel/2011-08/msg00494.html
> >>
> >> and a large amount of
On 2011-08-18, at 10:11 , Carl Sorensen wrote:
> On 8/17/11 10:41 PM, "Dan Eble" wrote:
>
>> What I have so far is a backtrace:
>> http://lists.gnu.org/archive/html/lilypond-devel/2011-08/msg00494.html
>> and a large amount of input spread across many files, which is why I chose to
>> review t
On 8/17/11 10:41 PM, "Dan Eble" wrote:
> Carl Sorensen byu.edu> writes:
>
>> Do you have more information about the segfault that you'd be willing to
>> share with us?
>
> What I have so far is a backtrace:
> http://lists.gnu.org/archive/html/lilypond-devel/2011-08/msg00494.html
> and a larg
Carl Sorensen byu.edu> writes:
> Do you have more information about the segfault that you'd be willing to
> share with us?
What I have so far is a backtrace:
http://lists.gnu.org/archive/html/lilypond-devel/2011-08/msg00494.html
and a large amount of input spread across many files, which is wh
On 8/16/11 11:15 PM, "Dan Eble" wrote:
> I think the following code should check that ev is not null before
> dereferencing it. This might be a factor in a segfault I saw. (Sorry to be
> so vague, but I am not going to build lilypond to test the theory. It would
> take a credible threat of
I think the following code should check that ev is not null before
dereferencing it. This might be a factor in a segfault I saw. (Sorry to be so
vague, but I am not going to build lilypond to test the theory. It would take
a credible threat of violence to change my mind.) A grep suggests tha
