Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Fri, 5 Oct 2001 11:09:18 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: console popping up unnecessarily in xterm (cygwin 1.3.3) Message-ID: <20011005110918.I13996@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.21i On Fri, Oct 05, 2001 at 11:21:20PM +0900, Kazuhiro Fujieda wrote: >>>> On 29 Sep 2001 01:57:13 -0000 >>>> danny@ishiboo.com (Danny Dulai) said: > >> 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 >> >> 2001-07-25 Kazuhiro Fujieda > >You're right. These patches of mine are related to your problem. >The first change caused the same problem on rxvt, so I made one >more change and managed to solve it. > >The same logic should also solve it on xterm. I guess another >bug disturbs it. As you may know, Cygwin DLL 1.3.3 has a bug >related to the inheritance of file descriptors in fork. It is >fixed in the recent development snapshots. AFAIK, the inheritance problem is just for socket descriptors. I don't think this qualifies. cgf -- 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/