X-Spam-Check-By: sourceware.org Date: Mon, 28 Aug 2006 11:24:37 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: cygwin snapshot 20060818 - lots of diagnostic output Message-ID: <20060828152437.GA12710@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <44F309C4.8060700@scytek.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44F309C4.8060700@scytek.de> User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk 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, Aug 28, 2006 at 11:20:36AM -0400, Volker Quetschke wrote: >Hi, > >after getting spurious "Resource temporarily unavailable" errors >with cygwin 1.5.21 (after the last M$ patch day!!) I decided to try >the latest cygwin snapshot on my favorite testcase - compiling OOo. Resource unavailable messages are often the result of running out of Windows heap space. There is not much that we can do about them other than suggest that people adjust the heap and that is not a foolproof solution. >The good news is that I haven't seen another "Resource temporarily >unavailable" error so far, but now there is a lot of diagnostic >output in the logfiles. See: > > >Are you interested in testcases? I could try to create one. We're always interested in *simple* test cases. As I've noted here previously, however, there are some false warning being generated by the snapshots currently. Please don't bother trying to report those. 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/