Frederik Ramm wrote: > Stefan de Konink wrote: >> if (mmap2(...) == -1) >> exit(-1); > > The problem is that between our program code (which is of course fast > and efficient) and the kernel (which offers the mmap2 system call) sits > a fat beast (a.k.a "dynamic programming language") named "ruby" that > magically frees the programmer of all responsibilities regarding memory > allocation and deallocation. This is good because it becomes hard for > even the stupidest programmer to create memory leaks, but on the other > hand the programmer is not usually told when ruby decides to make an > mmap call and what the return value of it was.
Even ruby probably isn't doing the mmap - that is probably glibc... Tom -- Tom Hughes ([EMAIL PROTECTED]) http://www.compton.nu/ _______________________________________________ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
