X-Spam-Check-By: sourceware.org
X-Server-Uuid: 241911D6-425B-44B9-A073-E3FE0F8FC774
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: Cygwin and Windows Vista Beta 2
Date: Tue, 6 Jun 2006 20:11:20 -0400
Message-ID: <EB48EBF3B239E948AC1E3F3780CF8F883B7298@MI8NYCMAIL02.Mi8.com>
From: "Chuck McDevitt" <cmcdevitt AT greenplum DOT com>
To: cygwin AT cygwin DOT com
X-WSS-ID: 6898C6211N48063835-01-01
Content-Type: text/plain;  charset=us-ascii
X-IsSubscribed: yes
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
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k570Bf8w024109

Just an FYI:  Cygwin's fork() implementation has an intermittent bug
when running on Windows Vista Beta 2 
(Beta 2 will be released to the general public soon).

Here's an example error (from running  bash -l ):

      6 [main] ? (3572) c:\cygwin\bin\bash.exe: *** fatal error -
couldn't alloc
ate heap, Win32 error 0, base 0x800000, top 0x810000, reserve_size
61440, allocs
ize 65536, page_const 4096
     62 [main] bash 4888 child_copy: stack write copy failed,
0x22E300..0x230000
, done 0, windows pid 2286132, Win32 error 5
bash: fork: No error

Here's another example (doing an ls inside bash):

bash-3.1$ ls
     20 [main] ? (5248) c:\cygwin\bin\bash.exe: *** fatal error -
couldn't alloc
ate heap, Win32 error 0, base 0x800000, top 0x820000, reserve_size
126976, alloc
size 131072, page_const 4096
137604415 [main] bash 4436 child_copy: stack write copy failed,
0x22E940..0x2300
00, done 0, windows pid 2287732, Win32 error 5
bash: fork: No error

The odd thing is that it sometimes works, and sometimes gives this
error.

Is it possible there were some "reserved for future use" parameters on
some Win32 calls that aren't getting initialized properly, and are now
being used by Vista?




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