On Sat, Mar 16, 2013 at 10:32:57PM +0100, Jörg F. Wittenberger wrote: > In fact assuming a stack corruption would explain it at least. > Especially since I'm observing various strange error messages > since I updated to chicken 4.8.2.
Does it happen often enough to perform a git bisect to track down the commit that introduced the bug? That would certainly help! Cheers, Peter -- http://www.more-magic.net _______________________________________________ Chicken-hackers mailing list Chicken-hackers@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-hackers
