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/
