X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-3.3 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_83,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By:	sourceware.org
To:	cygwin AT cygwin DOT com
From:	Mark Geisert <mark AT maxrnd DOT com>
Subject:	Re: 1.5.25: cygwin executeables are crashing from time to time (Windows 2003 Server Ver 5.2 Build 3790 Service Pack )
Date:	Wed, 15 Apr 2009 05:35:30 +0000 (UTC)
Lines:	29
Message-ID:	<loom.20090415T052340-361@post.gmane.org>
References:	<33936 DOT 203 DOT 47 DOT 149 DOT 67 DOT 1239673160 DOT squirrel AT 203 DOT 47 DOT 149 DOT 67> <20090414014542 DOT GA1681 AT ednor DOT casa DOT cgf DOT cx> <58812 DOT 203 DOT 47 DOT 149 DOT 67 DOT 1239674722 DOT squirrel AT 203 DOT 47 DOT 149 DOT 67> <loom DOT 20090414T045006-631 AT post DOT gmane DOT org> <49E52A4C DOT 6040008 AT lisec-sw DOT com>
Mime-Version:	1.0
User-Agent:	Loom/3.14 (http://gmane.org/)
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

Stefan Walter writes:
> Attached now the cygcheck.out. Maybe someone can give me now a hint for 
> the crashes.
> 
> Additional: There is no Antivirus as well as Firewall running on the System.
[...] 
> Cygwin Configuration Diagnostics
> Current System Time: Tue Apr 14 11:02:39 2009
> 
> Windows 2003 Server Ver 5.2 Build 3790 Service Pack 2
> 
> Running under WOW64 on AMD64
> 
> Running in Terminal Service session

Others may see something else in the cygcheck output you sent; thanks for
sending it.  What stood out to me is what's quoted above.  This kind of smells
like the "cygwin bash crashes on Win Serv 2008" thread from last October.  That
ended up with the realization that installing Terminal Service changes the
system-wide DEP (Data Execution Protection) flag for the worse, as far as Cygwin
is concerned.

Could you please read one of the later emails on that thread:
<http://cygwin.com/ml/cygwin/2008-10/msg00459.html>
and see if the situation applies to your systems and whether the workaround
works for you?  I know the thread talks about Windows Server 2008 and you're
running WS2K3, but maybe it applies there too.

..mark


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

- Raw text -