On Sat, Mar 09, 2013 at 01:33:50PM +0100, Christian Kellermann wrote: > * Jörg F. Wittenberger <[email protected]> [130309 12:26]: > > I'm afraid I have no idea how I could boil this down to a reproducible > > case. > > > > I've seen it once so far in a logfile of a process, which xreates > > approximately 2000000 threads a day when communicating over WAN > > with about ten peers plus all those public web access (approx. > > since chicken does not have unique thread numbers, but rscheme > > does; when I run the rscheme version instead I see thos 2^6 threads; > > though the chicken version has a different runtime behavior and does > > not share 100% of the code, hence it could use a different amount of > > threads.) > > I am confused. I thought you were wondering about a compilation > message you get during the flow analysis of the scrutinizer.
As I understood it, it's an exception's message upon an error at runtime. I think this may be an off-by-one error somewhere resulting in data corruption. I've seen similar mystifying error messages when the stack wasn't quite right; alomst everything is fine except it tells you something is wrong. You're right; if this can't be easily reproduced, we're unlikely to find a root cause. A core dump and access to the machine might help, but I'm unsure it crashes this hard. Cheers, Peter -- http://www.more-magic.net _______________________________________________ Chicken-hackers mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/chicken-hackers
