X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=1.2 required=5.0 	tests=AWL,BAYES_00,DEAR_WINNER,HELLO_DEAR
X-Spam-Check-By: sourceware.org
Date: Thu, 18 Dec 2008 13:47:42 +0100
From: Mojmir Svoboda <mojmir DOT svoboda AT illusionsoftworks DOT com>
To: cygwin AT cygwin DOT com
Subject: cygwin and vista x64
Message-ID: <20081218124742.GA4966@msvoboda>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-ICQ-UIN: 37571205
User-Agent: Mutt/1.5.17 (2007-11-01)
X-IsSubscribed: yes
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

hello dear cygwinners,

i have used cygwin happily until i got this new machine with vista x64
installed.

i'm perceiving a lot of "fork: resource temporarily unavailable"
problems.
there seems to be connection with bash which crashes most often, but if
i run for example make of bigger project, then echo and g++ crashes too.
i tried msys and i noticed similar problems.

// later note: now i got error: bash.exe: *** WFSO timed out after longjmp

i appologize for my ignorance, but i have no idea how do you debug
cygwin itself (i am not windows person). do i have to do debug build
or is there a symbol map available? do you use gdb, windbg or doest
debugger really matter? i'd really like to provide more info.

best regards,
mojmir

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