DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:from:to:references:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=rr84svYmRwUPkGF2
	ns6dyEqotGQmZ3ne+f2tpXN35lT+HGjajrVZQhBd0Gge9wBCIspEvyYcDZFhKoi7
	2k+V27OMdHGvr2sSDvOEpCx/BJ1Fi9ktOUDqnlvCKbwAEp4qibKEdm2L7kL+MRmU
	yNdmsKIRILGtRWBPSqm2xEleJwg=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: malloc(0) crashing with SIGABRT
From: =?UTF-8?B?UGV0ciBTa2/EjcOtaw==?= <pskocik@gmail.com>
To: cygwin@cygwin.com
References: <366918d8-b505-45be-dc28-303579f17341@gmail.com>
Message-ID: <78e19eb7-956e-cd05-a076-e56ce347bbbe@gmail.com>
Date: Mon, 9 Sep 2019 19:13:06 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <366918d8-b505-45be-dc28-303579f17341@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

There's been a twitter discussion on how different POSIX platforms
handle malloc(0): https://twitter.com/sortiecat/status/1170697927804817412 .

As for Cygwin, the answer appears to be "not well", but this should be
easy to fix.

Best regards,
Petr Skocik

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple