OK, I've made another pass and am getting different results. This leads me to believe that what I am seeing is a function of my runtime environment, and not due to the specific builds.
My theory is that the old builds are *just* enough smaller that -- most of the time -- they work with this weird repo, and that older builds are simply too much bigger to "fit" in my runtime environment. So the next step, I think, would be to make a 'valgrind' run and try to track down memory leaks. That's not going to happen tonight, it's too late for me. Sorry for all the confusion, but it looks like a fairly nasty little problem which fortunately is not common. Best, Ron _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
