Hi all, this is not strictly an error, just a DoS kind of catching it: when a program runs into a deadlock, chicken will endless loop telling me so.
I'm not sure how this should be handled. "Normal" exit with error might not be possible, since the finalisation process might deadlock too. Immediately exit with error might loose valuable data. Maybe the process should send itself a SIGSTOP? How could this be caught better than littering the terminal/logfile? best regards /Jörg _______________________________________________ Chicken-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/chicken-users
