Paul Scott writes:
> Ok. False alarm but hopefully useful info:
>
> The error was triggered by two instances of \times which should have
> been \time . Now my code compiles with either 2.17.13 or 2.17.14.
That's no excuse for segfaulting, however.
--
David Kastrup
__
On Wed, Mar 20, 2013 at 10:27:27AM +0100, David Kastrup wrote:
> Paul Scott writes:
>
> > I appreciate that possibility. I have said the same thing to a number
> > of programming classes I have taught including the assembly language
> > class I was teaching tonight.
>
> Sounds like you should b
Ok. False alarm but hopefully useful info:
The error was triggered by two instances of \times which should have been
\time . Now my code compiles with either 2.17.13 or 2.17.14.
If it helps I am using lilypond-2.17.14-1.linux-64
Maybe this difference between 2.17.14 and 2.17.13 could be relat
Paul Scott writes:
> I appreciate that possibility. I have said the same thing to a number
> of programming classes I have taught including the assembly language
> class I was teaching tonight.
Sounds like you should be able to run lilypond in a debugger then and
get a useful backtrace.
How di
On Wed, Mar 20, 2013 at 08:37:38AM -, Trevor Daniels wrote:
>
> Paul Scott wrote Wednesday, March 20, 2013 7:56 AM
>
>
> >I get segmentation faults with 2.17.14 on a medium to large set of files
> > which compile fine with 2.17.13. I have gotten these errors with some
> > other
> > recen
Paul Scott writes:
> I get segmentation faults with 2.17.14 on a medium to large set of files
> which compile fine with 2.17.13. I have gotten these errors with some
> other
> recent 2.17.xx versions. I don't believe I will get errors with a
> minimal example.
>
> What evidence can I provide t
"Trevor Daniels" writes:
> Paul Scott wrote Wednesday, March 20, 2013 7:56 AM
>
>
>>I get segmentation faults with 2.17.14 on a medium to large set of files
>> which compile fine with 2.17.13. I have gotten these errors with
>> some other
>> recent 2.17.xx versions. I don't believe I will get
Paul Scott wrote Wednesday, March 20, 2013 7:56 AM
>I get segmentation faults with 2.17.14 on a medium to large set of files
> which compile fine with 2.17.13. I have gotten these errors with some other
> recent 2.17.xx versions. I don't believe I will get errors with a minimal
> example.
>
I get segmentation faults with 2.17.14 on a medium to large set of files
which compile fine with 2.17.13. I have gotten these errors with some other
recent 2.17.xx versions. I don't believe I will get errors with a minimal
example.
What evidence can I provide that might help find the problem?
