Different behaviors of New operator - Dynamic memory allocation

pan64 · 08-01-2014, 05:42 AM

I found this in the man page of syscalls(2)

Quote:

The select(2) and mmap(2) system calls use five or more arguments, which caused problems in the way argument passing on the i386 used to be set up. Thus, while other architectures have sys_select() and sys_mmap() corresponding to __NR_select and __NR_mmap, on i386 one finds old_select() and old_mmap() (routines that use a pointer to a argument block) instead. These days passing five arguments is not a problem any more, and there is a __NR__newselect that corresponds directly to sys_select() and similarly __NR_mmap2.

Based on that it looks like old_mmap should not be used, but I'm not really familiar with it.

johnsfine · 08-01-2014, 08:53 AM

I think my answer in one of the OP's other threads completely explains the situation:

http://www.linuxquestions.org/questi...6/#post5213152

sundialsvcs · 08-01-2014, 09:37 AM

It may be the case that you will need to write your own "wrapper" around the memory-allocation areas of your program, to keep their own approximate count of how much memory they're requesting vs. the limitation that you wish to set. If they discover that they've exceeded their own quota, they basically kill themselves.

The problem with any "SOS = Short On Storage" situation is that it takes storage with which to sound the alarm.

Would a facility such as "ulimit" be applicable here?