From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/4756 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: malloc not behaving well when brk space is limited? Date: Mon, 31 Mar 2014 00:51:12 -0400 Message-ID: <20140331045112.GD26358@brightrain.aerifal.cx> References: <20140329170032.GJ8221@example.net> <20140329191502.072c07f9@vostro> <20140329172212.GW26358@brightrain.aerifal.cx> <20140329180229.GL8221@example.net> <20140329185619.GX26358@brightrain.aerifal.cx> <20140329195422.GM8221@example.net> <20140329202553.GA26358@brightrain.aerifal.cx> <20140329205409.GN8221@example.net> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1396241494 18521 80.91.229.3 (31 Mar 2014 04:51:34 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 31 Mar 2014 04:51:34 +0000 (UTC) Cc: musl@lists.openwall.com To: u-igbb@aetey.se Original-X-From: musl-return-4760-gllmg-musl=m.gmane.org@lists.openwall.com Mon Mar 31 06:51:27 2014 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1WUUBz-0002Pk-0x for gllmg-musl@plane.gmane.org; Mon, 31 Mar 2014 06:51:27 +0200 Original-Received: (qmail 28575 invoked by uid 550); 31 Mar 2014 04:51:26 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 28567 invoked from network); 31 Mar 2014 04:51:26 -0000 Content-Disposition: inline In-Reply-To: <20140329205409.GN8221@example.net> User-Agent: Mutt/1.5.21 (2010-09-15) Xref: news.gmane.org gmane.linux.lib.musl.general:4756 Archived-At: On Sat, Mar 29, 2014 at 08:54:09PM +0000, u-igbb@aetey.se wrote: > On Sat, Mar 29, 2014 at 04:25:54PM -0400, Rich Felker wrote: > > I have in mind a solution which may work as a real fix, not just a > > workaround. If it works out, it will probably make it into the 1.1.x > > series first, but it should apply cleanly to 1.0.0. > > This sounds great. > > > I'm pretty busy with some other work right now so it'll be at least > > a few days before I really get started on it I think. > > That's alright. I have got a workaround sufficient to continue > the building and testing but I will not commit/publish the built > applications yet. > > When a more tolerable malloc arrives I can rebuild from the beginning and > only then commit to production the resulting, proper and reconfigurable > incarnation. Nice. > > Tell me when you might need testing. Please see the patch on the mailing list. Rich