Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 21 Apr 2012 10:21:35 -0700
From:      Cy Schubert <Cy.Schubert@komquats.com>
To:        Dimitry Andric <dim@FreeBSD.org>
Cc:        Michael Pounov <misho@aitbg.com>, Jason Evans <jasone@canonware.com>, current@FreeBSD.org
Subject:   Re: /usr/bin/as: out of memory allocating 4194304 bytes after a  total of 524288000 bytes
Message-ID:  <201204211721.q3LHLZTa007501@slippy.cwsent.com>
In-Reply-To: Message from Dimitry Andric <dim@FreeBSD.org> of "Fri, 20 Apr 2012 22:37:18 %2B0200." <4F91C8FE.4070807@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
In message <4F91C8FE.4070807@FreeBSD.org>, Dimitry Andric writes:
> This is a multi-part message in MIME format.
> --------------030506060901050002030508
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> Content-Transfer-Encoding: 7bit
> 
> On 2012-04-20 22:21, Jason Evans wrote:
> > On Apr 20, 2012, at 1:14 PM, Jason Evans wrote:
> >> On Apr 20, 2012, at 1:10 PM, Dimitry Andric wrote:
> >>> On 2012-04-20 21:54, Jason Evans wrote:
> >>>> On Apr 20, 2012, at 12:49 PM, Dimitry Andric wrote:
> >>>>> I think the best solution would be for jemalloc to avoid using obvious
> >>>>> names like "chunksize" for its globals, because it is basically a
> >>>>> library that could be linked to any sort of program out there.
> >>>>>
> >>>>> For example, it could prefix all its internal-use only globals with
> >>>>> "jemalloc_" or some other mangling scheme.  Jason, any thoughts?
> >>>>
> >>>> jemalloc has optional namespace mangling support built in for just this 
> reason.  I'll turn it on, hopefully today.
> >>>
> >>> Indeed, I had just found jemalloc/internal/private_namespace.h. :)  It
> >>> does seem to list only functions, not variables, is that right?
> >>
> >> Ah right, functions only.  Well then, I don't have any bright ideas for so
> lving this problem in the short run.
> >
> > I take it back.  There's spotty mangling coverage for variables.  I'll try 
> to add full coverage.
> 
> I'm now using the attached.  It seems to work...

It didn't work for me.


-- 
Cheers,
Cy Schubert <Cy.Schubert@komquats.com>
FreeBSD UNIX:  <cy@FreeBSD.org>   Web:  http://www.FreeBSD.org





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201204211721.q3LHLZTa007501>