Re: X crashes with SIGPIPE

[Robert McBroom]

On 4/17/20 11:38 PM, 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.


Have a similar problem. How did you get the backtrace? Everything just 
closes for the X system and is gone for me.  Windows 10 Home. I've the 
same problem with a startxwin in a mintty window and with the entries to 
use wsl2 ubuntu or fedora.


Robert

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

Re: X crashes with SIGPIPE

[Henry Gebhardt via Cygwin]

On Mon, 2020-04-20 at 18:03 +0100, Jon Turney wrote:
> 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.

Yes, indeed! Also with "-nowgl", but I assume that is irrelevant.

> 
> > Thread 1 received signal SIGPIPE, Broken pipe.
> > [Switching to Thread 2952.0x1144]
> > 0x00010053f250 in _XSERVTransSocketWritev (ciptr=0xbb18,
> > buf=0xbc10, 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'.

Thank you for this. I will run with sigpipe ignored, and see if I can
reproduce then. Might be a few days until it triggers.

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


Best,
Henry

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

Re: X crashes with SIGPIPE

[Jon Turney]

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]
0x00010053f250 in _XSERVTransSocketWritev (ciptr=0xbb18,
buf=0xbc10, 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

X crashes with SIGPIPE

[Henry Gebhardt via Cygwin]

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.

Best,
Henry
$ gdb --pid=`pidof /usr/bin/XWin`
GNU gdb (GDB) (Cygwin 8.2.1-1) 8.2.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-pc-cygwin".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word".
Attaching to process 2952
[New Thread 2952.0x1144]
[New Thread 2952.0x2178]
[New Thread 2952.0x22c4]
[New Thread 2952.0x95c]
[New Thread 2952.0x3958]
[New Thread 2952.0x3e88]
[New Thread 2952.0x3cdc]
[New Thread 2952.0x474]
[New Thread 2952.0x35e0]
[New Thread 2952.0x4398]
[New Thread 2952.0x2f04]
[New Thread 2952.0x40c0]
[New Thread 2952.0x3d9c]
[New Thread 2952.0x2d10]
[New Thread 2952.0xb40]
[New Thread 2952.0x138]
[New Thread 2952.0x2f38]
[New Thread 2952.0x261c]
[New Thread 2952.0x3f98]
[New Thread 2952.0xcc0]
[New Thread 2952.0x3ee0]
[New Thread 2952.0x3c08]
[New Thread 2952.0x1670]
[New Thread 2952.0x2b7c]
[New Thread 2952.0x2bf0]
[New Thread 2952.0xbc8]
[New Thread 2952.0x128c]
Reading symbols from /usr/bin/XWin.exe...Reading symbols from 
/usr/lib/debug//usr/bin/XWin.exe.dbg...done.
done.
(gdb) c
Continuing.
[Thread 2952.0x128c exited with code 0]
[New Thread 2952.0x2530]
[New Thread 2952.0x3cd4]
[Thread 2952.0x2530 exited with code 0]
[Thread 2952.0x3cd4 exited with code 0]
[New Thread 2952.0x30b4]
[New Thread 2952.0x30a0]

Thread 1 received signal SIGPIPE, Broken pipe.
[Switching to Thread 2952.0x1144]
0x00010053f250 in _XSERVTransSocketWritev (ciptr=0xbb18,
buf=0xbc10, size=-17396) at /usr/include/X11/Xtrans/Xtranssock.c:2382
2382/usr/include/X11/Xtrans/Xtranssock.c: No such file or directory.
(gdb) bt full
#0  0x00010053f250 in _XSERVTransSocketWritev (ciptr=0xbb18,
buf=0xbc10, size=-17396) at /usr/include/X11/Xtrans/Xtranssock.c:2382
No locals.
#1  0x in ?? ()
No symbol table info available.
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(gdb)
Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 1.20.5.0
OS: CYGWIN_NT-10.0-18362 MT-210810 3.1.4-340.x86_64 2020-02-19 08:49 UTC x86_64
OS: Windows 10  [Windows NT 10.0 build 18362] (Win64)
Package: version 1.20.5-3 built 2019-09-06

XWin was started with the following command line:

/usr/bin/XWin :0 -multiwindow -listen tcp -nowgl -auth 
 /home/gebhardt/.serverauth.1895 

ddxProcessArgument - Initializing default screens
winInitializeScreenDefaults - primary monitor w 1920 h 1080
winInitializeScreenDefaults - native DPI x 120 y 120
[ 78029.546] (II) xorg.conf is not supported
[ 78029.546] (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information
[ 78029.546] LoadPreferences: /home/gebhardt/.XWinrc not found
[ 78029.546] LoadPreferences: Loading /etc/X11/system.XWinrc
[ 78029.546] LoadPreferences: Done parsing the configuration file...
[ 78029.546] winDetectSupportedEngines - RemoteSession: no
[ 78029.562] winDetectSupportedEngines - DirectDraw4 installed, allowing ShadowDDNL
[ 78029.562] winDetectSupportedEngines - Returning, supported engines 0005
[ 78029.562] winSetEngine - Multi Window or Rootless => ShadowGDI
[ 78029.562] winScreenInit - Using Windows display depth of 32 bits per pixel
[ 78029.578] winAllocateFBShadowGDI - Creating DIB with width: 1920 height: 1080 depth: 32
[ 78029.578] winFinishScreenInitFB - Masks: 00ff ff00 00ff
[ 78029.578] winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32
[ 78029.578] MIT-SHM extension disabled due to lack of kernel support
[ 78029.578] XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel
[ 78029.921] (II) IGLX: Loaded and initialized swrast
[ 78029.921] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[ 78030.109] winPointerWarpCursor - Discarding first warp: 960 540
[ 78030.109] (--) 3 mouse buttons found
[ 78030.109] (--) Setting autorepeat to delay=500, rate=31
[ 78030.109] (--) Windows keyboard layout: "0409" (0409) "US", type 4
[ 78030.109] (--) Found matching XKB configuration "English (USA)"
[ 78030.109] (--) Model = "pc105" Layout = "us" Variant = "none" Options = "none"
[ 78030.109] Rules =