"m...@apollinemike.com" <m...@apollinemike.com> writes: > On Nov 17, 2011, at 3:22 PM, lilyp...@googlecode.com wrote: > >> >> Comment #10 on issue 1723 by d...@gnu.org: beam fails to extend over >> rest, intermittently >> http://code.google.com/p/lilypond/issues/detail?id=1723 >> >> Previous comment 9 was a wrong lead, just a case of obfuscate >> programming. I'll likely commit some programming comments to save >> somebody else from wracking his brain, but that's about it for that >> last hunch. Search goes on. > > Using all of the suggestions proposed so far, I'm failing to reproduce > the error in all but the occasional regtest. > This has uninitialized variable written all over it. If someone can > get me a surefire buggy file, I can likely figure this out. The > challenge is getting the consistently buggy file.
Another idea of mine was order-dependency for iterating through a map or other hashing structure (in particular an eq?-hashtable or its C++ equivalent) that might involve memory addresses in its hash generation. -- David Kastrup _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
