From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 91451 invoked by alias); 12 May 2018 14:23:17 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 91433 invoked by uid 89); 12 May 2018 14:23:16 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=1741, corruption, rebuilding, his X-HELO: out2-smtp.messagingengine.com Received: from out2-smtp.messagingengine.com (HELO out2-smtp.messagingengine.com) (66.111.4.26) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 12 May 2018 14:23:14 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 9CF5725C6D; Sat, 12 May 2018 10:23:12 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Sat, 12 May 2018 10:23:12 -0400 X-ME-Sender: Received: from [192.168.1.102] (host86-160-189-108.range86-160.btcentralplus.com [86.160.189.108]) by mail.messagingengine.com (Postfix) with ESMTPA id 12270E4350; Sat, 12 May 2018 10:23:11 -0400 (EDT) Subject: Re: libharfbuzz0 1.7.6-1 update causing xwin-xdg-menu.exe to crash To: The Cygwin Mailing List References: <30aa068b-574f-8770-d8f3-eb037c038709@scrc.umanitoba.ca> <63a969f7-00eb-2067-7dbe-f141bfecbaae@dronecode.org.uk> <45934aef-f59b-7ca6-5cf9-8e60ad559cae@scrc.umanitoba.ca> Cc: Gilles Detillieux From: Jon Turney Message-ID: Date: Sat, 12 May 2018 14:27:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <45934aef-f59b-7ca6-5cf9-8e60ad559cae@scrc.umanitoba.ca> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2018-05/txt/msg00153.txt.bz2 On 26/04/2018 16:40, Gilles Detillieux wrote: > On 2018-04-26 09:03, Jon Turney wrote: >> On 19/04/2018 22:15, Gilles Detillieux wrote: >>> Has anybody else run into this problem? I've done two installations >>> of Cygwin/X on Windows 10 systems this week, and they both had >>> problems with the XWin Server dying just a few seconds after starting >>> up. I traced the problem back to xwin-xdg-menu.exe getting a >>> Segmentation fault, which then causes XWin Server to exit. I hacked >>> an alternate .startxwinrc file to prevent XWin Server from dying (it >>> ends with a "sleep infinity"), so I could debug it further. >>> >>> With the XWin Server running reliably, I then ran "strace >>> xwin-xdg-menu.exe" and saw that it got a segmentation fault just >>> after reading a TTF font from the Windows Font directory >>> (bahnschrift.ttf if it matters). I noticed there were two recent >>> library updates related to font handling, so I tried back out to the >>> previous version for each. It turns out that when I reverted to >>> version 1.7.4-1 of libharfbuzz0, xwin-xdg-menu.exe stopped crashing. >>> >>> If it matters, both these systems are the Fall Creator's Update >>> (1709) of Windows 10 64-bit, and I'm running the 32-bit version of >>> Cygwin. >>> >>> Hopefully someone can track down and fix this recent bug! >> >> Thanks for reporting this. >> >> I can reproduce this problem, but it only seems to occur with 32-bit >> cygwin. >> >> (Obviously you also need a recent enough Windows 10 to have the >> Bahnschrift font) >> >> The actual crash seems to be in fontconfig, e.g. 'fc-query >> /usr/share/fonts/microsoft/bahnschrift.ttf' fails in the same way. Another possible workaround seems to be to blacklist this particular font, e.g.: create a /etc/fonts/conf.d/local.conf containing: /usr/share/fonts/microsoft/bahnschrift.ttf >> I didn't get very far investigating the problem, as rebuilding the >> fontconfig package with the current toolchain seems to be enough to >> make the problem go away. > > Thanks for the follow-up and narrowing down the problem, Jon. > Interesting that rebuilding fontconfig clears up the issue. Although, if > it's a memory corruption issue, it could just be that the new toolchain > lays things out differently enough that the bug doesn't manifest itself > the same way. It could also be that the new gcc fixes a compiler or > optimizer bug that led to the problem. Perhaps you and Yaakov could > touch base on which toolchain versions you're using and see if an update > to his toolchain may be in order. > > Are you using the test version of gcc (7.3.0-1) announced April 11, or > the older release. I've got gcc-core-6.4.0-5 on mine, which I assume is > the latest stable release. The latest stable release, 6.4.0-5. -- 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