delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com> |
List-Archive: | <http://sourceware.cygnus.com/ml/cygwin/> |
List-Post: | <mailto:cygwin AT sourceware DOT cygnus DOT com> |
List-Help: | <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs> |
Sender: | cygwin-owner AT sourceware DOT cygnus DOT com |
Delivered-To: | mailing list cygwin AT sourceware DOT cygnus DOT com |
Message-ID: | <393648B6.76F7556E@fri.uni-lj.si> |
Date: | Thu, 01 Jun 2000 13:27:50 +0200 |
From: | Robert DOT Rozman AT fri DOT uni-lj DOT si (Robert Rozman) |
X-Mailer: | Mozilla 4.51 [sl] (WinNT; I) |
X-Accept-Language: | sl |
MIME-Version: | 1.0 |
To: | cygwin AT sourceware DOT cygnus DOT com |
Subject: | Memory access restrictions under cygwin NT ? |
Hello, I ran into weird behaviour of compiled programs that I ported from Linux to cygwin. It seems like they cannot allocate as much space for arrays as they would normally be able to do under Linux (both machines have similar memory configuration - cygwin under NT has more virtual memory space). Is cygwin somehow restricted in accessing memory space under win NT ? If not, sorry I've caused my problem. :-) Thanks in advance. Regards, Robert Rozman rozman AT fri DOT uni-lj DOT si -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |