DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:reply-to:mime-version:to
	:cc:subject:references:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=eY+eoMBBvvx2j72r
	V/nwHvL1n8WY5kh2PXMVeEXLByOlTMPkJpDRjzkKVcCRAKwHyaUPXcHyKo6OemCs
	oMRCdJtszV6/4x7MqNCGZ+NEs8x0dQpdR7X6ePhefQC6hw8/Z4f3GUr5gCnykwo5
	aF0RoaNpJROV1EB1BgU2SC2Sj6M=
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
Message-ID: <52EBAC18.3010505@dronecode.org.uk>
Date: Fri, 31 Jan 2014 13:58:48 +0000
From: Jon TURNEY <jon DOT turney AT dronecode DOT org DOT uk>
Reply-To: cygwin AT cygwin DOT com
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
CC: l DOT wood AT surrey DOT ac DOT uk
Subject: Re: How to destroy a cygwin terminal
References: <290E20B455C66743BE178C5C84F1240847E63346FB AT EXMB01CMS DOT surrey DOT ac DOT uk>
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E63346FB@EXMB01CMS.surrey.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On 31/01/2014 08:58, l DOT wood AT surrey DOT ac DOT uk wrote:
> In cygwin X window, type:
> 
> cd /
> ls */*/*

Heh. What an interesting bug.

However, it doesn't seem to be an X server bug.  Typing the same commands into
a mintty causes that to exit as well.

> xinit: connection to X server lost
> 
> waiting for X server to shut down winClipboardProc - winClipboardFlushWindowsMessageQueue trapped WM_QUIT message, exiting main loop.
> winClipboardProc - XDestroyWindow succeeded.
> winClipboardIOErrorHandler!
> winMultiWindowXMsgProcIOErrorHandler!
> winInitMultiWindowXMsgProc - Caught IO Error.  Exiting.
> winDeinitMultiWindowWM - Noting shutdown in progress
> (EE) Server terminated successfully (0). Closing log file.

On 31/01/2014 13:13, Marco Atzeri wrote:
>> for what I can see the xterm crash, not the Xserver

What is happening here is that the X server has been started with xinit or
startx, and the command is typed into the initial xterm.  When that exits, the
X server is shut down to.

>> and I will bet when you are looking on /proc/*/*

Wrong guess :)
'ls proc/*/*' doesn't seem to reproduce it, but 'ls dev/*/*' does.

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