public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: "Larry W. Virden" <lvirden@gmail.com>
To: cygwin-xfree@cygwin.com
Subject: Re: Trying to find a solution for segmentation fault crashes in the most recent x server provided by setup.exe
Date: Wed, 23 May 2012 12:50:00 -0000	[thread overview]
Message-ID: <CAPRVdgTjbf-gaSji92KDXuGrCQxht5unQXP3TzEPH+x5yzwtzQ@mail.gmail.com> (raw)
In-Reply-To: <CAPRVdgQO0vu44t+3zmUF7s6_H4Nxuye-fAJRvJhS6_dY6Rbo3w@mail.gmail.com>

Well we continue to discover new things about our specific situation
with xfree server crashes.

This may in fact be a general cygwin problem rather than xfree. What
we are finding is a change in general process handling.

During our original testing - on windows 7 32-bit - we tested scripts
we had developed under XP that prompt the user for information about
the server, login, etc. and then start the x server and invoke the
cygwin xterm or mintty to perform an ssh -Y to the server as the login
specified.
The code looked at the processes, identified whether or not the server
was running, and, if not, launches a new server. Otherwise, the code
skips that step and goes on to start the terminals.

After testing, a deployment decision was made to move to windows 7 64 bit
 instead.

We assumed that everything would continue to work as tested.

What we are seeing, now however, is that we are getting multiple X
servers started. Even worse, we are seeing processes like bash, ssh,
mintty, and xterm hanging around after the user has closed the
windows.

We are looking into why the script is no longer seeing the X server
process running.

But the fact that those processes are sticking around after the
windows are closed seems to be an issue.

Anyways, as soon as someone tries to use windows attached to more than
one of the running X servers, then we see crashes. Not all the servers
crash, which really caused us a lot of confusion - we would get error
messages saying the server had crashed, but occasionally xterms would
still be running, etc.

I am a bit surprised that the X server itself doesn't prevent someone
from starting a second version on the same cpu/disk/cygwin instance.
But perhaps there is some use for that kind of special functionality.

Has anyone else seen similar behaviors?

--
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:[~2012-05-23 12:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-22 19:19 Larry W. Virden
2012-05-23 12:50 ` Larry W. Virden [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=CAPRVdgTjbf-gaSji92KDXuGrCQxht5unQXP3TzEPH+x5yzwtzQ@mail.gmail.com \
    --to=lvirden@gmail.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).