the problem appears to be detected here: /sys/src/libc/port/pool.c:833: printblock(p, b, "mem user overflow");
so either your memory has gone wonky or the kernel is writing past the end of the buffer. this must be in the kernel where the overflow is occuring. it appears the reason you don't panic on the spot is because of this: /sys/src/9/port/alloc.c:28: .flags= POOL_TOLERANCE, if you're feeling brave, you could recompile without POOL_TOLERANCE and try to recreate the problem. it'd be nice to know who's screwing up. but .. that's not too much fun when you have an all-in-wonder box. maybe make a copy of fossil's stuff before trying. - erik
