>>>> "BAW" == Barry A Warsaw
<barry(a)python.org> writes:
BAW> Can you say more about what "playing poorly" means? What
BAW> symptoms should we be looking for? What problems have been
BAW> reported?
What has been observed on my Debian system is a SIGSEGV crash in the
build. The bleeding edge Red Hat people are seeing a crash in build
or a crash in X startup. Since I don't understand at all what's
causing the crash, I'm assuming the worst: memory corruption that
could strike anytime, anywhere. You're not necessarily safe if XEmacs
starts.
ISTR that a change in glibc initialization caused similar problems a
couple of years back by screwing up the structures we use to keep
track of unexec'd data. If this is something similar, then --pdump
might be the solution. --with-system-malloc also seems to help, but I
don't know why (especially since AFAIK we _do_ use the system malloc
on Linux).
--
Institute of Policy and Planning Sciences
http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.