> I haven't yet tried posting a query to a FreeBSD list, as it could simply > be a bug on amd64, but I was wondering whether there was anything (other > than deactivating tests and documenting use of ulimit -v on this > platform) that could be done to work around this behaviour.
I think it should be possible to debug this (for people with access to such a system, and appropriate skills). I find it hard to believe that a large malloc will simply crash the process, rather than returning NULL. More likely, there is a NULL returned somewhere, and Python (or libc) fails to check for it. Regards, Martni _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
