DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 6C30C3858D31
From: Jon Turney <jon.turney@dronecode.org.uk>
Subject: Re: X crashes with SIGPIPE
To: The Cygwin Mailing List <cygwin@cygwin.com>
References: <faff3a3252644ab0f41d02854413932c9932e7af.camel@gmail.com>
Message-ID: <a4840a16-3739-a340-8c1f-23ad10b0d48c@dronecode.org.uk>
Date: Mon, 20 Apr 2020 18:03:36 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Thunderbird/68.7.0
MIME-Version: 1.0
In-Reply-To: <faff3a3252644ab0f41d02854413932c9932e7af.camel@gmail.com>
Content-Language: en-GB
Precedence: list
Cc: Henry Gebhardt <hsggebhardt@gmail.com>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: cygwin-bounces@cygwin.com
Sender: "Cygwin" <cygwin-bounces@cygwin.com>

On 18/04/2020 04:38, Henry Gebhardt via Cygwin wrote:
> Hi,
> 
> Cygwin/X crashes every few days for me. I managed to obtain a backtrace
> from the last crash (attached). Server log is also included.
> 
> I have not, yet, managed to pin down the exact trigger for the crash. I
> am running two graphical programs under Windows 10 WSL2 Debian: tilix
> and evince.
> 
> Thank you for any help.

Thanks for reporting this issue.

I am assuming, although it's not totally clear from your report, that 
you are starting the X server with '-listen tcp', and are setting 
DISPLAY to localhost:0.0 or similar in your WSL environment.

> Thread 1 received signal SIGPIPE, Broken pipe.
> [Switching to Thread 2952.0x1144]
> 0x000000010053f250 in _XSERVTransSocketWritev (ciptr=0xffffbb18,
>     buf=0xffffbc10, size=-17396) at /usr/include/X11/Xtrans/Xtranssock.c:2382
> 2382    /usr/include/X11/Xtrans/Xtranssock.c: No such file or directory.

I'm not sure this is the actual point of failure (since the X server 
should be setting SIGPIPE to be ignored), so you probably need to tell 
gdb not to stop on it e.g. 'handle sigpipe ignore'.

In any case, a sigpipe here indicates that the X client has already 
closed when the X server tries to write to it's socket.

Assuming gdb is giving accurate information here, this is also looks 
very odd, as a negative value of size (which is used as iovcnt passed to 
write) doesn't make a lot of sense.
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple