X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:cc:reply-to:from
	:message-id:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=b8pXqbjhZLU2/+1L
	jrAzF9DlZLLG+BJXhQ7qi4USXjEFmlilwA9ktE5RqiFgAWRE1EnSRN4jLS5ToK75
	nFPjHG8tP7xHgR49LlE1GcCrHsIa+ZEY+uPNtAYZ/T9rW49GFFBmUq1e7jXGFbbk
	9atldyqWkFTJa4zktfMgXWu4CA0=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:cc:reply-to:from
	:message-id:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=tCCocekVX5EAJSYpOWW3sO
	DLWTU=; b=lCyZowm3Fnh9qhvDxhx4Zl5DXM6Wlb6uEXiG3Y3xifu77gfyM+1AdP
	iTj+lPNeXEvkKkM4X83yiiQ182KT99KLHHAf6KwR3J140tl6ynLLt59J5eKBWkh4
	nOdyTHQrQxeFYIXmUMKpuGi2fLze9vMLLP4hTq92jU31miZCnjySg=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-2.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=H*F:D*uk, H*RU:sk:host86-, H*F:D*org.uk, Hx-spam-relays-external:sk:host86-
X-HELO:	out2-smtp.messagingengine.com
X-ME-Sender:	<xms:RNzhWmA-vwp-H5IxPOH6Ils5v9_55H2Fr2avXwUP9XcQLqrRPV8gXw>
Subject:	Re: libharfbuzz0 1.7.6-1 update causing xwin-xdg-menu.exe to crash
To:	The Cygwin Mailing List <cygwin AT cygwin DOT com>
References:	<30aa068b-574f-8770-d8f3-eb037c038709 AT scrc DOT umanitoba DOT ca>
Cc:	Gilles Detillieux <grdetil AT scrc DOT umanitoba DOT ca>
Reply-To:	The Cygwin Mailing List <cygwin AT cygwin DOT com>
From:	Jon Turney <jon DOT turney AT dronecode DOT org DOT uk>
Message-ID:	<63a969f7-00eb-2067-7dbe-f141bfecbaae@dronecode.org.uk>
Date:	Thu, 26 Apr 2018 15:03:45 +0100
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:	<30aa068b-574f-8770-d8f3-eb037c038709@scrc.umanitoba.ca>

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.

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.

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

- Raw text -