From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Cc: Henry Gebhardt <hsggebhardt@gmail.com>
Subject: Re: X crashes with SIGPIPE
Date: Mon, 20 Apr 2020 18:03:36 +0100 [thread overview]
Message-ID: <a4840a16-3739-a340-8c1f-23ad10b0d48c@dronecode.org.uk> (raw)
In-Reply-To: <faff3a3252644ab0f41d02854413932c9932e7af.camel@gmail.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.
next prev parent reply other threads:[~2020-04-20 17:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-18 3:38 Henry Gebhardt
2020-04-20 17:03 ` Jon Turney [this message]
2020-04-20 23:08 ` Henry Gebhardt
2021-01-25 20:23 ` X intermittent crashes with SIGSEGV when resizing windows Henry Gebhardt
2020-04-22 17:05 ` X crashes with SIGPIPE Robert McBroom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a4840a16-3739-a340-8c1f-23ad10b0d48c@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin@cygwin.com \
--cc=hsggebhardt@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).