Date: Fri, 7 Mar 2008 19:37:24 +0100 From: Erik Trulsson <ertr1013@student.uu.se> To: Jason Evans <jasone@FreeBSD.org> Cc: freebsd-stable@freebsd.org, Joshua Coombs <jcoombs@gwi.net> Subject: Re: FreeBSD 7 buildworld error Message-ID: <20080307183724.GA79858@owl.midgard.homeip.net> In-Reply-To: <47D1735D.60007@FreeBSD.org> References: <1204313564l.249966l.0l@psu.edu> <7E228F3A-DFE0-4071-8694-14A012CC21E1@gothic.net.au> <1204575279l.807074l.0l@psu.edu> <fqrqch$bh2$1@ger.gmane.org> <47D1735D.60007@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Mar 07, 2008 at 08:54:53AM -0800, Jason Evans wrote: > Joshua Coombs wrote: >> Derek Taylor wrote: >>> On Fri, Feb 29, 2008 09:50 PM Sean <sean@gothic.net.au> wrote: >>>> Check /etc/make.conf for CFLAGS, and if present remove it. >>> >>> This fixed the problem. >>> >>> Thank you. >>> >>> -Derek. >> >> I can confirm a failure in the same spot. What concerns me is in both my >> failure, and Derek's, the malloc is failing well below what limit says >> should be allowed. >> >> bin/cc/cc_int/../cc_tools >> -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc >> -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config >> -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcclibs/include >> -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcclibs/libcpp/include >> -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcclibs/libdecnumber >> -I/usr/obj/usr/src/tmp/legacy/usr/include -c ../cc_tools/insn-attrtab.c >> >> cc1: out of memory allocating 136475392 bytes >> *** Error code 1 >> >> Stop in /usr/src/gnu/usr.bin/cc/cc_int. >> *** Error code 1 >> >> cyrix-dlc# limit >> cputime unlimited >> filesize unlimited >> datasize 524288 kbytes >> stacksize 65536 kbytes >> coredumpsize unlimited >> memoryuse unlimited >> vmemoryuse unlimited >> descriptors 957 >> memorylocked unlimited >> maxproc 478 >> sbsize unlimited >> >> cc1 was only trying to request 130MB, my datasize is 512MB, why did it >> fail? > > It looks to me like gcc is trying to allocate a single 130MiB object, but > you don't say anything about how much memory is already in use. It may > well be that there are no remaining places in the memory map to place such > a large object. And that particular file (insn-attrtab.c, which is a machine-generated part of gcc itself,) is known to require much more memory to compile than most other source files. If gcc runs out of memory anywhere during a buildworld it is most likely when compiling that particular file. -- <Insert your favourite quote here.> Erik Trulsson ertr1013@student.uu.se
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080307183724.GA79858>