desj@brahms.BERKELEY.EDU (David desJardins) (08/22/86)
There definitely appears to be some sort of bug in Larn 12.0 that causes it occasionally to scribble over the scoreboard. Here is what our scoreboard looked like after the last time it happened (I have converted control char- acters to ^x form to avoid munging terminals): ^O^A^X Do you re^H^@ly want to quit? ^AYes^B or ^ANo^B please? Do you want to quit? ^AYes^B or ^ANo^B please? Do you want to quit^E^@ ^AYes^B or ^ANo^B please? Do you want to quit? ^AYes^B or ^ANo^B please? Do you want to quit? ^AYes^B or ^ANo^B^D^@lease? Do you want to quit? [ ... 20 similar lines deleted ... ] ^AYes^B or ^ANo^B please? Do you want to quit? ^AYe^@^@ or ^ANo^B please? Do you want to quit? ^[[;H^[[2J^@^@^@^@^@^@^@^@^@^@^B^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^I^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^H^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^G^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^ @^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^F^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^E^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ Obviously the bug is in the quit routine, but before I go digging into the code I thought I would ask if anyone else has seen and/or solved this problem. BTW, we are running larn suid, so the program must in fact have done this. And it has happened at least twice now. It is also annoying because when the program tries to read this munged scorefile the result is a seg fault. It would obviously be better if the program detected that the scorefile was not readable and created a new one. -- David desJardins