X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Mon, 21 Sep 2009 14:37:56 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: [1.7] gvim "Cannot fork" error Message-ID: <20090921183755.GB16647@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20090921022457.GA32232@ednor.casa.cgf.cx> <4AB73096.9030407@users.sourceforge.net> <20090921144827.GA15626@ednor.casa.cgf.cx> <4AB7A633.6060002@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4AB7A633.6060002@gmail.com> User-Agent: Mutt/1.5.20 (2009-06-14) 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 Mon, Sep 21, 2009 at 05:13:39PM +0100, Dave Korn wrote: >Christopher Faylor wrote: >>I can say that any DLL built with cygwin-1.7.0-51 - cygwin-1.7.0-56 is >>probably suspect. That's 2009-07-13 - 2009-08-13 . > >Argh, that's my fault isn't it? Sorry for not figuring out we should >have done this when we first fixed that bug and thanks for putting in >the debugging effort. Yeah, it's your "fault". But, of course, you introduced a new mechanism to fix a very longstanding problem. Some kinks are to be expected. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple