Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Injected-Via-Gmane: http://gmane.org/ To: cygwin AT cygwin DOT com From: Rolf Campbell Subject: Re: [ANNOUNCEMENT] Updated: cygwin-1.3.21-1 Date: Wed, 12 Mar 2003 18:02:22 -0500 Lines: 34 Message-ID: References: <20030312173132 DOT C16261C221 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet AT main DOT gmane DOT org User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030210 X-Accept-Language: en-us, en In-Reply-To: <20030312173132.C16261C221@redhat.com> Christopher Faylor wrote: > I've made a new version of the Cygwin DLL and associated utilities > available for download. As usual, a list of what has changed is below. > > - Fix setsid problem where processes did not correctly detach from a > console. (Christopher Faylor) I commonly run a compilation from within GNU Emacs. I've never had any problems with this until I tried running 1.3.21-1. I think it has to do with the changes to the console handling. Here's a silly little program: #include #include int main(int numArgs, char** args) { spawnl(_P_WAIT, "C:/cygwin/bin/ls", "C:/cygwin/bin/ls", NULL); return 0; } If I compile it without -mno-cygwin, then everything is fine (tried rxvt & emacs). If it is compiled with -mno-cygwin, it still works fine in rxvt, but when run from within bash, within Emacs, it allocates a console, writes its stdout to that console, then closes it's console. For a large compile, this means that 1000's of consoles are popping up and dissapearing, not only slowing things down, but also loosing the stdout from that non-cygwin app. -Rolf -- 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/