Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Date: Tue, 3 May 2005 11:05:46 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: side effects of Cygwin's maximum memory test
Message-ID: <20050503090546.GD25050@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <1148ee1105050215253ad27030 AT mail DOT gmail DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1148ee1105050215253ad27030@mail.gmail.com>
User-Agent: Mutt/1.4.2i

On May  3 00:25, Utku Ozcan wrote:
> I *think* that the test below, which tests memory allocation limit of
> Cygwin *might* produce problems in Windows XP:
> 
> http://sources.redhat.com/cygwin/cygwin-ug-net/setup-maxmem.html
> 
> In this page, I have compiled the C code, and after having run the
> compiled executable, Windows XP gave suddenly a warning that virtual
> memory setting has been changed (I think, that repeated malloc() calls
> in this code somehow change the virtual memory settings in Windows
> XP).

Not really.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

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