X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Mon, 29 Sep 2008 15:13:11 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: crash if fork(2) from another thread Message-ID: <20080929191311.GB12323@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <003301c92110$336cee20$0200a8c0@whiterabc2znlh> <20080928033013.GA2040@ednor.casa.cgf.cx> <002001c92160$e2fae400$0200a8c0@whiterabc2znlh> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <002001c92160$e2fae400$0200a8c0@whiterabc2znlh> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Sun, Sep 28, 2008 at 08:53:55PM +0900, Hirokazu Yamamoto wrote: >cgf wrote: >>Your test case worked fine for me with Cygwin 1.7.x. I don't have a >>copy of 1.5.x handy to test. >> >>"crash" is an imprecise term. You need to read >>http://cygwin.com/problems.html. > >I'll attach the result of "cygcheck -s -v -r > cygcheck.out" You still didn't explain what "crash" means, that was why I pointed you at a web page which goes to some effort in trying to make it clear that you should be descriptive when reporting problems. However, I did create a Vista VM with Cygwin 1.5.25 and saw that the code did not work. It is a bug in 1.5.25 but it is not going to be fixed since we are actively pursuing 1.7 now. 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/