Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191130044926.GR16318@brightrain.aerifal.cx>
Date: Fri, 29 Nov 2019 23:49:26 -0500
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: New malloc - first preview

On Fri, Nov 29, 2019 at 06:41:08PM +0200, Roman Yeryomin wrote:
> On Thu, Nov 28, 2019 at 11:56 PM Rich Felker <dalias@...c.org> wrote:
> >
> > Work on the new malloc is well underway, and I have a draft version
> > now public at:
> >
> > https://github.com/richfelker/mallocng-draft
> 
> Hi Rich,
> will it cover this problem: https://www.openwall.com/lists/musl/2018/02/09/4 ?

Yes. This is the main initial motivation for redoing malloc. I haven't
run that specific test case, but I have one which should be roughly
equivalent and it passes fine (no exploding heap usage).

Rich

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.