DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:message-id:date:mime-version
	:content-type:content-transfer-encoding; q=dns; s=default; b=qfM
	ovZ5wwsh6PuGWF/HcvMzqVuMv4nBwgrsDpGB3nMaezsJ2tLWyHmQSPTNmS4dRAfa
	FTKSc6jvtirdquoQA/ct7q1v43s5pgLnM7Y6guotBhjMcHZXY4mPYqQASic3p/zf
	USObrSJrpNVP8XJGrCivi5bH+/Srcbuk4WsQffow=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
From: Gilles Detillieux <grdetil AT scrc DOT umanitoba DOT ca>
Subject: libharfbuzz0 1.7.6-1 update causing xwin-xdg-menu.exe to crash
Message-ID: <30aa068b-574f-8770-d8f3-eb037c038709@scrc.umanitoba.ca>
Date: Thu, 19 Apr 2018 16:15:15 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

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

-- 
Gilles R. Detillieux              E-mail: <grdetil AT scrc DOT umanitoba DOT ca>
Spinal Cord Research Centre       WWW:    http://www.scrc.umanitoba.ca/
Dept. of Physiology and Pathophysiology, Rady Faculty of Health Sciences,
Univ. of Manitoba  Winnipeg, MB  R3E 0J9  (Canada)


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