X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 	tests=AWL,BAYES_20,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: Thu, 30 Apr 2009 07:13:08 +0000 (UTC)
Lines: 31
Message-ID:  <loom.20090430T070223-40@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> <loom DOT 20090415T052340-361 AT post DOT gmane DOT org> <49F94325 DOT 5060703 AT lisec-sw DOT com>
Mime-Version:  1.0
Content-Type:  text/plain; charset=us-ascii
Content-Transfer-Encoding:  7bit
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:
> >> 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 
[...]
> I have changed the DEP as well as i was trying with peflags. Nothing 
> seems to work.
> 
> I am getting a critical situation, if there is no fix available.
> 
> Does anyone have some further tips, how to solve the problem?

You can't be the only Cygwin user running on WS2K3; I do this using a WS2K3 VM
for instance.  I wonder if you're the only user on WS2K3 using Cygwin through
Terminal Service, though.  Do the errors still occur when you run from the
machine's console rather than through Terminal Service?  Something else to check
is whether moving "C:\cygwin\bin" to the front of your PATH makes any difference.

What cgf said early on still applies: the address reported in the Windows Event
Log for these faults doesn't make any sense as a cygwin1.dll address.  So
something in your environment seems confused.  Without somebody else reproducing
this we're left to shooting in the dark...

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