Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Date:	29 Sep 2001 01:57:13 -0000
Message-Id:	<Liam.1001728633.534708.15417.245609177@mergioo>
Mime-Version:	1.0
From:	danny AT ishiboo DOT com (Danny Dulai)
To:	cygwin AT cygwin DOT com
Subject:	console popping up unnecessarily in xterm (cygwin 1.3.3)
X-Mailer:	Liam [version 0.7]
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id f8SIxv807809

I'm trying to track down the change in cygwin 1.3.3 that caused consoles to
pop-up necessarily in xterm. background to this problem is in the thread
with a subject of "strange behavior regarding new cygwin 1.3.3 and cmd.exe"


I was looking briefly at the change log, and noticed these two changes:

2001-08-24  Kazuhiro Fujieda  <fujieda AT jaist DOT ac DOT jp>

        * syscalls.cc (check_tty_fds): New function.  Check whether there is a
        fd referring to pty slave.
        (setsid): Don't detach console if the process has a pty slave.


2001-07-25  Kazuhiro Fujieda  <fujieda AT jaist DOT ac DOT jp>

        * syscalls.cc (setsid): Detach process from its console if the current
        controlling tty is the console and already closed.
        * dtable.h (class dtable): Add members to count descriptors referring
        to the console.
        * dtable.cc (dtable::dec_console_fds): New function to detach process
        from its console.
        (dtable::release): Decrement the counter of console descriptors.
        (dtable::build_fhandler): Increment it.
        * exception.cc (ctrl_c_handler): Send SIGTERM to myself when catch
        CTRL_SHUTDOWN_EVENT.


Both look suspicious, and were made between the 1.3.2 and 1.3.3 releases.

Any suggestions to help solve this issue?

-- 
                                            _________________
                                            danny AT ishiboo DOT com

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -