Graham Percival <gra...@percival-music.ca> writes: > On Sun, Jul 31, 2011 at 10:04:59AM +0200, David Kastrup wrote: >> But this bug has been reported as occuring non-deterministically even in >> successive runs on the same machine, and there are rather few things >> that can introduce such stochastic behavior (another possibility would >> be timer-triggered garbage collection). > > In C++ code, I'd suspect some uninitalized variables (especially > since it always seems to work on the second run on a machine that > failed in the first run).
Modern operating systems don't give your code any leftovers from a previous run. That would be a security violation. And even user stack initialization below the stack pointer is not stochastical. System processes (like those triggered by interrupts and/or preemption) use their own stack, and again: it would be a security violation if a user process could access any information from their operation. So the sources for variation in successive identical runs are very limited. -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
