[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Check for null pointer

From: Carl Sorensen
Subject: Re: Check for null pointer
Date: Thu, 18 Aug 2011 08:11:37 -0600

On 8/17/11 10:41 PM, "Dan Eble" <address@hidden> wrote:

> Carl Sorensen <c_sorensen <at>> 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:
> and a large amount of input spread across many files, which is why I chose to
> review the lilypond source first.
> It may also be of interest that I am generating PartCombineMusic with scheme
> functions other than the stock part combiner.
> --
Two questions:

1) Is the segfault repeatable?

2) If so, can you test it on the latest development release?

I seem to recall a recent issue (although I can't find it in the git history
or in the tracker) of kill-mmrest being called on a multi-measure rest that
was already dead.  IIRC, it was fixed.

This could easily be the source of your segfault, given the kill-mmrest call
in your stack trace.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]