X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=AzZ2/+lvGXWTp2/QoE+EqYL+8epmTD07T95EaTNp+Km
	h9zQZIK7PYNS5fUnc2ddnN/XBK+57Dp51tl4B1j9kZkqfxq3fTWPv2HGhdjdktjQ
	KS8JT5EGTlY7i53i1xexNlSCyAas0hRWCktBuGJ29zghf8q96X58buaTsqLhm6xo
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=fapaCzf1yKh+eDa8OPgN1/PM0HQ=; b=ALrvQXtTN4qq/beXF
	yrjApIsVzdRGjCkDcxtuOwfUg+UTuOsquIoCbd4SdwYWmvn9RieeCcfFtP1oeC2Z
	8ko//EBTOjhGt7CyMUlpLylmeKODMM7aJ7SN2VldzMQnOtgCIZhjMLHR6EgZgqFT
	NeUc8jnAOtKu9BxhwdLibxhz3U=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_NEUTRAL autolearn=no version=3.3.2
X-HELO: bureau94.ns.utoronto.ca
Message-ID: <525D48E4.4070802@cs.utoronto.ca>
Date: Tue, 15 Oct 2013 09:53:40 -0400
From: Ryan Johnson <ryan DOT johnson AT cs DOT utoronto DOT ca>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Cygwin64: allocating too much memory causes a crash (corrected)
References: <lhgu299sucj7inkevs5h0plt38emrpmos4 AT 4ax DOT com> <20131015081829 DOT GA19383 AT calimero DOT vinschen DOT de>
In-Reply-To: <20131015081829.GA19383@calimero.vinschen.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

On 15/10/2013 4:18 AM, Corinna Vinschen wrote:
> On Sep 10 18:02, Bengt Larsson wrote:
>> (I'm sorry I attached the wrong file. This should be right.)
>>
>> On Cygwin64, if I malloc too much memory I get a stackdump, instead of a
>> NULL in return (for example testmalloc 5000000000).
> Sorry for the late reply, I was abroad for a couple of weeks.
>
> I just tried it myself and could easily reproduce the problem.
> I found the culprit in mmap.  It was using DWORD instead of size_t
> for a variable which was used for rounding purposes.
You know, this might be only the second 32->64 migration hiccup I've 
seen since the dust settled (the other being in gettimeofday or some such).

That's really impressive, given the number of places in the code where a 
DWORD (or other 32-bit value) could make things go really wrong...

Ryan


--
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