DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:references:cc:to:reply-to:from
	:message-id:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=aTjMVTCVyNCUaK9h
	ndKpAA8H+DSSPwCUPbtWhK9blVCNBmfXePYVvyqkbgPOFDnOt8PRTdySTktqylkl
	VfG1bm0Y8v9J8j5On5R0WioH0GQwC6XvVlqTRMOzeP2VWsM0lleMiO6t52dzkq8x
	pJvi5mWFrUnZIQLOCvVmi9mG8JM=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Subject: Re: startx-xwin seg fault, signal 11
References: <22057.9358902343$1436990254 AT news DOT gmane DOT org>
Cc: Bob Goldberg <bgoldberg AT homeaccess DOT com>
To: cygwin AT cygwin DOT com
Reply-To: cygwin AT cygwin DOT com
From: Jon TURNEY <jon DOT turney AT dronecode DOT org DOT uk>
Message-ID: <55A7C5BD.5080402@dronecode.org.uk>
Date: Thu, 16 Jul 2015 15:54:53 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.0.1
MIME-Version: 1.0
In-Reply-To: <22057.9358902343$1436990254@news.gmane.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

On 15/07/2015 20:56, Bob Goldberg wrote:
> I've been running cygwin/x (x86) under xp pro for YEARS,
> with it working perfectly.
>
> The last update to 1.17 has been a disaster.
> I've read about using -listen tcp, and DISPLAY=:0.0 ;
> however, nothing I've tried resolves the seg fault error i'm getting.
>
> using 1.17.1-5; have also tried 1.17.2-0 to no avail; back on 1-5.
>
> any help or direction would be appreciated!

Thanks very much for reporting this problem

Unfortunately, 32-bit XP is one of the platforms I test on, but I can't 
reproduce this problem.

There are two things you can perhaps do to generate additional 
information which will help me try to fix the problem:

1.
Install the experimental xorg-server-cygwin-crashreporter package and 
report the crash when it occurs.

2.
Follow the instructions for "Generating a backtrace when the X server is 
crashing at startup" at [1].

[1] http://x.cygwin.com/devel/backtrace.html

> Could not load crashreporter dll
> Welcome to the XWin X Server
> Vendor: The Cygwin/X Project
> Release: 1.17.1.0
> OS: CYGWIN_NT-5.1 myxppropc 2.0.4(0.287/5/3) 2015-06-09 12:20 i686
> OS: Windows XP Service Pack 3 [Windows NT 5.1 build 2600] (Win32)
> Package: version 1.17.1-5 built 2015-06-02
>
> XWin was started with the following command line:
>
> /usr/bin/X :3 -auth /home/bob/.serverauth.4656
>
> ddxProcessArgument - Initializing default screens
> winInitializeScreenDefaults - primary monitor w 1440 h 900
> winInitializeScreenDefaults - native DPI x 96 y 96
> [104131.312] Could not load crashreporter dll
> [104131.343] Fatal signal received in thread 0x20000038 [0x1164]
> [104131.343] (EE) Segmentation fault at address 0x1
> [104131.484] (EE) /usr/bin/xorg-backtrace failed with returncode 0
> [104131.484] (EE) Fatal server error:
> [104131.484] (EE) Caught signal 11 (Segmentation fault). Server aborting
> [104131.484] (EE) Server terminated with error (1). Closing log file.

-- 
Jon TURNEY
Volunteer Cygwin/X X Server maintainer

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