From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Cc: Fabio Rossi <rossi.f@inwind.it>
Subject: Re: segfault in xwin-xdg-menu.exe
Date: Sat, 12 May 2018 14:43:00 -0000 [thread overview]
Message-ID: <80298918-f7ae-d4a3-d120-fe526dc28443@dronecode.org.uk> (raw)
In-Reply-To: <1904055421.570427.1526059466228@mail.libero.it>
On 11/05/2018 18:24, Fabio Rossi wrote:
>> Il 11 maggio 2018 alle 19.12 Ken Brown <kbrown@cornell.edu> ha scritto:
>>
>> On 5/11/2018 11:29 AM, Fabio Rossi wrote:
>>
>>> I have just made a fresh cygwin installation on windows 10 pro 32bit using setup 2.891. I have selected xorg-server, xinit, vim and gdb packages. I have modified the Xwin server configuration as described in https://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-startxwinrc-exit and later I have successfully started it by using the action "cygwin-x\xwin server" under Windows programs menu. The X server is running with display :0.0 and its icon is visible in the tray bar.
>>>
>>> On another system installed months ago I have the xdg menu application already running (it's automatically started by the xwin startup script) but I didn't need to follow the above mentioned trick described in the FAQ.
>>>
>>> In a cygwin terminal I then try starting manually xwin-xdg-menu by using:
>>>
>>> $ DISPLAY=:0 xwin-xdg-menu.exe
>>>
>>> but I get a segmentation fault. With gdb I get the following backtrace:
>>>
[...]
>>>
>>> It seems a problem with fontconfig. Any hint?
>>
>> Could it be the same problem as this?
>>
>> https://cygwin.com/ml/cygwin/2018-04/msg00325.html
>>
>
> Thanks for the reference, it seems the same problem. I have tried stracing the problem, but I don't see a clear failure in the trace log. The size is quite large, it's ~ 245 kB when bzipped, if someone is interested I can post it somewhere later.
>
Yeah, this is the same problem, which is under investigation.
See also https://cygwin.com/ml/cygwin/2018-05/msg00152.html for another
workaround.
--
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
next prev parent reply other threads:[~2018-05-12 14:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-11 15:38 Fabio Rossi
2018-05-11 15:54 ` Marco Atzeri
2018-05-11 16:26 ` Fabio Rossi
2018-05-11 16:46 ` Marco Atzeri
2018-05-11 17:25 ` Ken Brown
2018-05-11 20:28 ` Fabio Rossi
2018-05-12 14:43 ` Jon Turney [this message]
2018-05-14 12:35 ` Fabio Rossi
2018-05-14 21:50 ` 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=80298918-f7ae-d4a3-d120-fe526dc28443@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin@cygwin.com \
--cc=rossi.f@inwind.it \
/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).