X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.4 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SARE_MSGID_LONG40,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By:	sourceware.org
MIME-Version:	1.0
In-Reply-To:	<b5c76c9d1003291821u47091b1cg98a0e020ea15ca27@mail.gmail.com>
References:	<b5c76c9d1003291708h79aa0e3cx214cb6bb8d001521 AT mail DOT gmail DOT com> <b5c76c9d1003291821u47091b1cg98a0e020ea15ca27 AT mail DOT gmail DOT com>
Date:	Mon, 29 Mar 2010 18:39:21 -0700
Message-ID:	<b5c76c9d1003291839k5dfd7238gbf55d11279365605@mail.gmail.com>
Subject:	Re: 1.7.2 on 2008 SP2: man segfaults + X problems
From:	Mark McConnell <markd DOT mcconnell AT gmail DOT com>
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

2010/3/29 Mark McConnell <markd DOT mcconnell AT gmail DOT com>:
> 2010/3/29 Mark McConnell <markd DOT mcconnell AT gmail DOT com>:
>> I am running the XWin X Server
>> Release: 1.7.6.0 (10706000)
>> Build Date: 2010-03-22
>>
>> After installing Cygwin 1.7.2 for the first time on Windows Server
>> 2008 SP2, I discovered several indications of a problem with my Cygwin
>> installation. I describe 4 "symptoms" below.
>>
>> SYMPTOM 1
>> =A0man* dumps core after a Segmentation fault
>>
>> $ man man
>> Segmentation fault (core dumped)
>>
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> ...
>
> In addition to man segfaulting, dgb also dumps core - which is
> inconvenient for tracking down what's going on with man. =A0 But they
> leave such a small dump, I've attached the stackdump from both man.exe
> and dbg.exe to this message.
>
> Mark
> --


I realized after reading these stackdumps, that this sort of
STATUS_ACCESS_VIOLATION failure is what I should expect from Windows
Data Execution Prevention being turned on.  I turned this off for
man.exe, and now man is able to work.  SYMPTOM 1 is resolved.

Mark
--

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -