public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Yusuke Tamura <tamura@hpc-sol.co.jp>
To: cygwin-xfree <cygwin-xfree@cygwin.com>
Cc: klindsay@ucar.edu, Yusuke Tamura <tamura@hpc-sol.co.jp>
Subject: Re: X segmentation fault when particular application attempts to open a window
Date: Fri, 27 Apr 2012 00:39:00 -0000	[thread overview]
Message-ID: <30CD240E1F5702tamura@hpc-sol.co.jp> (raw)
In-Reply-To: <4F9990D0.9040103@dronecode.org.uk>

Jon,

thank you for the update! XWin is working as before.

I appreciate your prompt action very much.

Yusuke

>On 25/04/2012 22:45, Keith Lindsay wrote:
>> On 4/25/2012 2:20 PM, Keith Lindsay wrote:
>>> I'm running a data analysis program called ferret on a remote machine
>>> that I've logged on to with "ssh -X". When the program attempts to
>>> create a window, the Cygwin/X server crashes with a segmentation fault.
>>> The seg fault is reproducible.
>>>
>>> xclock works fine from the same remote machine.
>>>
>>> This is with version 1.12.0-4 of xorg-server.
>>>
>>> ferret has worked with some previous versions of the Cygwin/X server,
>>> but I'm not certain about the precise version where the breakage
>>> occurred. I backed up one version and encountered the same problem.
>>>
>>> I've attached the output of "cygcheck -c", the file
>>> /var/log/xwin/XWin.0.log, and the output of a gdb that is attached to
>>> the XWin process when it crashes.
>> 
>> I realized that I can back up to other versions of xorg-server by 
>> installing
>> from the local directory that contains previous version downloads. I have
>> discovered that ferret works fine with version 1.12.0-1 of xorg-server 
>> (built
>> 2012-03-12) and generates the segmentation violation with version 1.12.0-2
>> (built 2012-04-04).
>
>Thanks for the excellent bug report.
>
>I've uploaded 1.12.0-5 which hopefully contains a fix for this crash.
>
>This crash was caused by the server being unable to find the bitmap which the
>application wants to use for it's icon, it's not clear why this is happening,
>so I would be interested to know if the application icon is correct or not.
>
>-- 
>Jon TURNEY
>Volunteer Cygwin/X X Server maintainer

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/


      parent reply	other threads:[~2012-04-27  0:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-25 20:20 Keith Lindsay
2012-04-25 21:45 ` Keith Lindsay
2012-04-26 18:15   ` Jon TURNEY
2012-04-26 20:22     ` Keith Lindsay
2012-04-27  0:39     ` Yusuke Tamura [this message]

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=30CD240E1F5702tamura@hpc-sol.co.jp \
    --to=tamura@hpc-sol.co.jp \
    --cc=cygwin-xfree@cygwin.com \
    --cc=klindsay@ucar.edu \
    /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).