public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Gilles Detillieux <grdetil@scrc.umanitoba.ca>
To: cygwin@cygwin.com
Subject: Re: libharfbuzz0 1.7.6-1 update causing xwin-xdg-menu.exe to crash
Date: Tue, 24 Apr 2018 21:30:00 -0000	[thread overview]
Message-ID: <dd650fe0-46ab-99c4-8b0e-641f8f38350b@scrc.umanitoba.ca> (raw)
In-Reply-To: <30aa068b-574f-8770-d8f3-eb037c038709@scrc.umanitoba.ca>

I just ran into this bug on a third Windows 10 1709 64-bit system, only 
this time it was a little worse. Both xwin-xdg-menu.exe and xterm.exe 
would crash. An strace on xterm.exe showed the crash occurring after 
reading that same font, but it happened even when I reverted 
libharfbuzz0 to the 1.7.4-1 version. On this system, I also had to 
revert libfreetype6 from 2.8.1-1 to 2.6.5-1 to get xterm and 
xwin-xdg-menu to run reliably. Something in the font handling in these 
two libraries broke on a recent update.

On 04/19/2018 04:15 PM, 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,
> Gilles
>

-- 
Gilles R. Detillieux              E-mail: <grdetil@scrc.umanitoba.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

  reply	other threads:[~2018-04-24 21:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-19 21:15 Gilles Detillieux
2018-04-24 21:30 ` Gilles Detillieux [this message]
2018-04-26 14:03 ` Jon Turney
2018-04-26 15:40   ` Gilles Detillieux
2018-05-12 14:27     ` Jon Turney
2018-05-14 19:29       ` Gilles Detillieux
2018-05-14 21:44         ` Jon Turney
2018-05-15 15:01           ` Gilles Detillieux
2018-05-14 21:38   ` Brian Inglis
2018-05-14 21:47     ` Jon Turney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=dd650fe0-46ab-99c4-8b0e-641f8f38350b@scrc.umanitoba.ca \
    --to=grdetil@scrc.umanitoba.ca \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).