On 2012-12-30, Volker Braun <[email protected]> wrote: > ------=_Part_795_4463763.1356883427560 > Content-Type: text/plain; charset=ISO-8859-1 > > On Sunday, December 30, 2012 1:20:24 PM UTC, Dima Pasechnik wrote: > >> I think it's just the matter of setting up a fresh signal handler before >> calling mmap(), and reinstating the old one after this is done. >> > > No, if you mmap() with MAP_NORESERVE then it always succeeds (if the > processor can address it, 16TB on x86_64). Reads always succeed. But > whenever you write to the memory map, you can get a SIGSEGV.
I think that also depends upon /proc/sys/vm/overcommit_memory (see manpages for proc(5)). As well, can't one just set the appropriate ulimit? Attempts to go over a ulimit don't lead to SIGSEGV, right? Dima -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
