In article <20140128141231.ga3...@britannica.bec.de>, Joerg Sonnenberger <jo...@britannica.bec.de> wrote: >On Tue, Jan 28, 2014 at 08:55:37AM +0200, Alan Barrett wrote: >> On Mon, 27 Jan 2014, Christos Zoulas wrote: >> >Modified Files: >> > src/sys/arch/i386/include: vmparam.h >> > >> >Log Message: >> >Cut down MAXDSIZE from 3G to 2.5G otherwise bottomup allocation ends up >> >supplying an out of bounds hint for sigcode (c001e000 > bf000000). Makes >> >a.out binaries work again. >> >> Will this make malloc fail 0.5GB earlier than before? > >Which malloc? jemalloc uses mmap and doesn't count against MAXDSIZE.
Bottomup allocations count against maxdsize, topdown don't. Nevertheless, I restored the limit back to where it was. christos
