delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2000/12/24/23:57:25

Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Mon, 25 Dec 2000 13:56:51 +0900
From: <wakamiya AT osaka DOT email DOT ne DOT jp>
X-Mailer: EdMax Ver2.32.4F
MIME-Version: 1.0
To: Kazuhiro Fujieda <fujieda AT jaist DOT ac DOT jp>
Cc: cygwin AT cygwin DOT com
Subject: Re: malloc problem
In-Reply-To: <s1svgs98fka.fsf@jaist.ac.jp>
References: <s1svgs98fka DOT fsf AT jaist DOT ac DOT jp>
Message-Id: <E14APgq-0003Hh-00@ns.jcm-go.com>

Hello Fujieda san.

Kazuhiro Fujieda <fujieda AT jaist DOT ac DOT jp> wrote:
> It is a configurable limitation of the Cygwin DLL. You can
> control it through a registry entry.
I have modified registry entry using attached registry file and 
I am able to allocate a large memory block.
Thank you for your quick reply.

Yours faithfully,




--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019