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 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: fixed, sorta - 20040225 snapshot problem + gdb/cygpath/others runtime error Date: Fri, 27 Feb 2004 13:04:51 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Richard Campbell" To: X-IsSubscribed: yes Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id i1RI54Ae031256 After running a windows update, which installed some 12 critical patches for windows 2000, and 4 optional ones, the gdb/cygpath/others crash has disappeared. example of the problem: C:\cygwin>cygpath 28 [main] ? 2608 init_cheap: Couldn't reserve space for cygwin's heap, Win3 2 error 487 c:\cygwin\bin\cygpath.exe (2608): *** AllocationBase 0x0, BaseAddress 0x616A0000 , RegionSize 0x1AE0000, State 0x10000 So there does appear to be some combination of windows 2000 settings that hose the february snapshots, but current from microsoft as of 2/27/2004 seems to fix them. There was no difference (or than system time and hard drive free space) between a cygcheck -s -v -r from the broken system and the working system. This is for the archives, mostly. -Richard Campbell. -- 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/