X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient:	djgpp AT delorie DOT com
Subject:	Re: valloc() returns NULL for larger requests, but malloc works fine
To:	djgpp AT delorie DOT com
References:	<3459b672-8f4d-9840-5a01-246db011ed06 AT assembler DOT cz>
	<a3a22537-8b52-4c56-a06e-5d0e5741e6a5 AT googlegroups DOT com>
	<7020918f-80d2-4dc8-ba7c-7b1cd946d3da AT googlegroups DOT com>
	<681c7486-3ec7-5dc3-5a8d-d4d8b8500feb AT assembler DOT cz>
From:	"Andris Pavenis (andris DOT pavenis AT iki DOT fi) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
Message-ID:	<5f509765-e04d-a437-0d49-284f7a58ebe1@iki.fi>
Date:	Tue, 2 Jan 2018 11:44:42 +0200
User-Agent:	Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
	Thunderbird/52.5.2
MIME-Version:	1.0
In-Reply-To:	<681c7486-3ec7-5dc3-5a8d-d4d8b8500feb@assembler.cz>
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On 01.01.2018 21:36, Rudolf Marek (r DOT marek AT assembler DOT cz) [via 
djgpp AT delorie DOT com] wrote:
> Hi.
>
> Dne 31.12.2017 v 04:43 rugxulo AT gmail DOT com [via djgpp AT delorie DOT com] napsal(a):
>> I don't think this needs a full libc re-release. But I doubt they're
>> willing to waste much time anyways.
>>
>> If you need it that badly, just put a .ZIP somewhere with the patch
>> and compiled (single?) .o file inside, and forget about it.
> Well the point is that someone else will spent time debugging same issue over and over again.
>
> Should I open a bug report instead?
>

No need for separate bug report.

Corresponding change is already in CVS. There are several accumulated 
changes since v2.05 in CVS. So perhaps I could put new packages in 
djgpp/beta/v2 or djgpp/alpha/v2 after some other changes will be in. 
Later a new version (2.06) could be released.

Andris

- Raw text -