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 Date: Sat, 3 Jan 2004 13:19:03 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: new snapshot with some tty/WinMe fixes Message-ID: <20040103181903.GA9424@redhat.com> Mail-Followup-To: cygwin AT cygwin DOT com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com I managed to get a WinMe installation up and running here so I can now debug some of the problems that show up there. And, they were interesting problems indeed. It seems like something sometimes starts up a stray thread on WinMe and that thread does not register itself with the new signal handler. It somehow doesn't even go through the DLL thread initialization code. So, all of my new code which allows signals to threads got confused by this. I've worked around this in an ugly way but at least I am not seeing the random failures that I was consistently getting. I will run the testsuite on this soon to see if it there are any more gotchas but I thought I'd get a new version uploaded. I also noticed YA handle leak in the new tty inheritance code with my old friend vfork, so I have hopefully fixed that. I tried all of the test cases that Pierre previously reported but I'm sure I missed one. I didn't change any of the fork handling, AFAIK, just vfork. That means that /bin/sh and make are potentially affected. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/