Charles-Francois Natali <neolo...@free.fr> added the comment: It was a long time ago, but: - I think the interpreter will never be able to catch all memory allocation errors, since because of overcommitting (which Linux does), you can very well get a segmentation fault even if the memory allocation routine (be it malloc or mmap) is successful (i.e. doesn't return NULL): so basically, we don't have any way to avoid that, since we will segfault only when we first touch the allocated page - since your application was "overflowing internal cache", this might very well be what happened (or it could have been a memory corruption issue :-)
Peers ? ---------- nosy: +neologix _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue5091> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
