From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13298 invoked by alias); 28 Jun 2012 14:05:15 -0000 Received: (qmail 13281 invoked by uid 22791); 28 Jun 2012 14:05:13 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_20,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from smtpout.karoo.kcom.com (HELO smtpout.karoo.kcom.com) (212.50.160.34) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 28 Jun 2012 14:05:00 +0000 Received: from 213-152-38-55.dsl.eclipse.net.uk (HELO [192.168.1.108]) ([213.152.38.55]) by smtpout.karoo.kcom.com with ESMTP; 28 Jun 2012 15:04:58 +0100 Message-ID: <4FEC6498.5030400@dronecode.org.uk> Date: Thu, 28 Jun 2012 14:05:00 -0000 From: Jon TURNEY Reply-To: cygwin-xfree User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: cygwin-xfree@cygwin.com CC: boxer@bytezeppelin.com Subject: Re: XWin 1.12.1.0 seg faults on startup? References: <4FD37A84.3000402@bytezeppelin.com> <4FDDE517.6090205@dronecode.org.uk> <4FE29762.6070003@bytezeppelin.com> <4FE86913.2010706@dronecode.org.uk> <4FEB27C1.7040905@bytezeppelin.com> In-Reply-To: <4FEB27C1.7040905@bytezeppelin.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-xfree-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-xfree-owner@cygwin.com Reply-To: cygwin-xfree@cygwin.com Mail-Followup-To: cygwin-xfree@cygwin.com X-SW-Source: 2012-06/txt/msg00035.txt.bz2 On 27/06/2012 16:33, Nick Vasilatos wrote: >> You might try creating an empty ~/.startxwinrc (so the default xterm is not >> started by startxwin) and see if that makes a difference? > > Would seem not/seems to fail as before. See below and log attached. Okay. thanks for trying anyhow. This is going to be somewhat problematic to debug since the debugger seems unable to attach to the faulted process. I'm not sure what might cause that, if it's some software you have installed which is interfering with Cygwin or some security policy you have set? Are you running XWin under a local Administrator account? I've uploaded a new snapshot at [1], can you try running that, adding the -notrapsignals option to your usual command line. This should generate a XWin.exe.stackdump file when it crashes. Can you attach that to an email, please. [1] ftp://cygwin.com/pub/cygwinx/XWin.20120628-git-59d15f68d4fd9bb8.exe.bz2 -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/