[Top][All Lists]

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

Re: Blocage aléatoire de LilyPond

From: address@hidden
Subject: Re: Blocage aléatoire de LilyPond
Date: Wed, 17 Apr 2013 08:48:36 +0300

On 17 avr. 2013, at 08:36, David Kastrup <address@hidden> wrote:

> Keith OHara <address@hidden> writes:
>> mike <at> mikesolomon.org <mike <at> mikesolomon.org> writes:
>>> This just hit the French list, which is an old bug already talked about
>>> in 2010:
>>> http://lists.gnu.org/archive/html/lilypond-devel/2010-11/msg00057.html
>>> It may be worth it to add a report.
>> The forwarded French email reports random crashes when compiling a
>> large file, for which the reporter sees no hope for making a minimal
>> example, with the error message showing the program terminating in
>> code written by Mike but since removed by him.
>> I see no hope for finding the problem, if it still exists in the
>> current version, from this information.
>> The linked email describes what seems to be a quite different problem.
> Mike did not bother explaining his deductions, but it would appear to me
> his claim would be that both are the same problem, but in 2.16.1 it
> blows up in a different place (temporary code from Mike) rather than the
> previous place.  So the problematic file would, when debugged by Mike,
> still throw errors in current LilyPond, just completely different errors
> from what the original poster reported for 2.16.1.
> So the 2010 problem is still around, it is just that the error
> tracebacks moved to Mike's code in 2.16 and have now moved on or back.
> -- 
> David Kastrup

Yup - the code that triggers this bug has existed for a long time.  It has 
since been pushed around and rears its head in different places but it still 
triggers the bug.


reply via email to

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