public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: "Matt D." <matt@codespunk.com>
To: cygwin-xfree@cygwin.com
Subject: Re: xinit hangs on XWin infinite loop when using -displayfd
Date: Mon, 21 Jul 2014 15:49:00 -0000	[thread overview]
Message-ID: <53CD368C.3060509@codespunk.com> (raw)
In-Reply-To: <53CC6789.4000601@codespunk.com>

Still hangs with the latest 1.15.1-4 release.

On my main machine, I get the following output:

$ xinit -- -displayfd 1

read display number ':0' from X server
0

On the VM it just hangs. Taskmanager shows xinit.exe waiting or hung 
with XWin.exe churning cycles and eating memory; about 4kB a tick.

Also on the VM, if I run the following:

$ xinit -- -displayfd

Then the display will open. So it seems to be an issue with whatever 
code is dealing with the file descriptors.


Matt D.

On 7/20/2014 9:06 PM, Matt D. wrote:
> The operating system is Windows XP Professional. It is a CLEAN install
> on a VMware virtual machine and is 100% patched up. Cygwin also is a
> clean install. I did try a rebaseall with no effect.
>
> This is the first time I've encountered this. When I run "xinit --
> -displayfd 3", xinit will hang and XWin takes up 100% of the cpu.
>
> I've confirmed that file descriptors are working:
>
> $ exec 3>a
> $ echo "test" >&3
> $ cat a
> test
> $ exec 3>&-
>
> I can confirm that ports are available and that both xinit and XWin work
> without this argument by running:
>
> $ xinit --
>
> Everything else works fine but without "-displayfd" I can't record where
> the display is for this session to disk.
>
> I've also tried copying known-working Cygwin installs into the VM and
> still have the same error. Copying the erroring install from the VM
> outside and running it on my development machine (Windows 7 x64) does
> not generate an error.
>
> Unless something stands out here, I can provide the VMware image for
> testing (how convenient).
>
>
> Matt D.
>
> --
> 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/
>
>
>

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


  reply	other threads:[~2014-07-21 15:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-21  1:06 Matt D.
2014-07-21 15:49 ` Matt D. [this message]
2014-07-21 16:00   ` Matt D.
2014-07-21 17:30     ` Matt D.
2014-07-28 12:35       ` Jon TURNEY
2014-07-28 23:57         ` Matt D.
2014-08-04 15:57           ` 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=53CD368C.3060509@codespunk.com \
    --to=matt@codespunk.com \
    --cc=cygwin-xfree@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).