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, 19 Feb 2005 14:17:53 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: cygwin bughunt (Jip-hee!) Message-ID: <20050219191753.GA25880@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <79F81D5F4790D344B05F489CE2AC8AB71468DD AT dubexdc03 DOT dubex DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <79F81D5F4790D344B05F489CE2AC8AB71468DD@dubexdc03.dubex.net> User-Agent: Mutt/1.4.1i On Fri, Feb 18, 2005 at 11:29:38AM +0100, David Dindorp wrote: >Christopher Faylor wrote: >>>The test were performed with 1.5.10-3, as newer versions call upon me >>>all sorts of other problems and thus can't be pushed to the failing box >>>right now. >>> >>>>Btw, I urge everyone to try the latest cygwin snapshot! This quote comes from a thread that suggested cygwin had mind control powers. If that was really true, you'd be using a snapshot by now. >>>Will do. Has the problem been found that results in this error?: *** >>>MapViewOfFileEx(0x188, in_h 0x188) failed, Win32 error 6 I don't know. You didn't produce a test case and I could never reproduce the problem. I did take a stab at fixing it and made some changes in that code so the error message will be different now, at least. >>2) You can *try* a snapshot to see if it fixes your problem. > >"Will do" sort of implies that that was exactly the course of action I >was contemplating :-). And asterisks around *try* implies that you should stop talking about it and start *doing* it. It is possible that this problem has been fixed by my recent attempts to correct the dreaded "hyperthreading" problem. However, if it hasn't been fixed, I'm not willing to debug problems in 1.5.10. It would be a fruitless endeavor. The code has changed in the last six months and, even if the problem was tracked down, we're not going to be releasing a new version of 1.5.10. If you want help, either use a snapshot or CVS. 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/