From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pj1-x1041.google.com (mail-pj1-x1041.google.com [IPv6:2607:f8b0:4864:20::1041]) by sourceware.org (Postfix) with ESMTPS id EDC4B384A87E for ; Mon, 20 Apr 2020 23:08:55 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org EDC4B384A87E Received: by mail-pj1-x1041.google.com with SMTP id e6so531326pjt.4 for ; Mon, 20 Apr 2020 16:08:55 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=qiB8ZqJQhcrSpXkoAg08zeJsy+k4cF3w5tENGKzPTtQ=; b=qD2dkfKhBgkv0ONjq/Y58m7JhU3WbIV/BTzl/VFjSSMd1oxQ1rKRMh2hDG2Ku1WAf4 VVyky7YjjxJGFdpil5aFtJdO+uK1nSb2OylDubASNfBFeX4bvYvFrM9PvajSgDKIh3My 72yIrxdmWoFu3PzIE5aKCNAm7F7/uKYjydXZZ2VTMEnDF8OEhRJPoAXJQC5FoKOjl74d qCJQB0Aof816evcYXKt18+MOCMCJchyznqEgWrhtykaRuqmw4jfTMENNQiV5xWJ86d+d mWVcZHyE4cc85jMO/6lVQzPz+tD1oioAgnwTt0jL5vCg0wNgaWLsKBAxZK7pZ6NTuH5o Liig== X-Gm-Message-State: AGi0PuZFi3BoAg0GdF/5yHcujbMUDfialczrmhWidWbYJpprw5NPEqV/ G30k0tLrFN5NF784xVzW1RY= X-Google-Smtp-Source: APiQypIwUJbvbACtL8v0UXtUvmneOOpyz4K8lQscbrURCgHRHqukzMIDbKh1uPZNzSIoV99FTVL88g== X-Received: by 2002:a17:90a:5a:: with SMTP id 26mr2119774pjb.74.1587424134921; Mon, 20 Apr 2020 16:08:54 -0700 (PDT) Received: from talman.lan (047-051-058-005.biz.spectrum.com. [47.51.58.5]) by smtp.gmail.com with ESMTPSA id 62sm549408pfu.181.2020.04.20.16.08.52 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 20 Apr 2020 16:08:53 -0700 (PDT) Message-ID: Subject: Re: X crashes with SIGPIPE From: Henry Gebhardt To: Jon Turney , The Cygwin Mailing List Date: Mon, 20 Apr 2020 16:08:51 -0700 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.30.5-1.1 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Apr 2020 23:08:58 -0000 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] > > 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'. 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