X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org From: "Dave Korn" To: References: <006801c85873$1230cad0$36926070$@humphrey AT comcast DOT net> <478E7E55 DOT 6010109 AT cygwin DOT com> Subject: RE: setup.exe 2.573.2.2 is crashing in Windows XP Date: Thu, 17 Jan 2008 14:14:51 -0000 Message-ID: <01df01c85913$5328c290$2e08a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <478E7E55.6010109@cygwin.com> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id m0HEFeie017105 On 16 January 2008 22:00, Larry Hall (Cygwin) wrote: > Alan Humphrey wrote: >> I'm having the same problem, only on Vista. >> >> >> Visual Studio Debugger reports: >> >> Unhandled exception at 0x004ac7e3 in setup.exe: 0xC0000005: Access >> violation reading location 0x01a1ff3c. >> >> Event Viewer says: >> >> Faulting application setup.exe_unknown, version 0.0.0.0, time stamp >> 0x46821e21, faulting module setup.exe, version 0.0.0.0, time stamp >> 0x46821e21, exception code 0xc0000005, fault offset 0x000ac7e3, process id >> 0x12a8, application start time 0x01c858701d7a3b44. >> >> Note: setup.exe reports its version as 2.573.2.2 >> >> I installed an older version of setup (2.510.2.2) from another box and it >> worked just fine. > > There's a debug version of 2.573.2.2 and two later versions (2.575 and > 2.578) available as snapshots at > if you're interested in tracking things down/trying out other options. I suspect this could be the corrupted .lst.gz file in /etc/setup problem that we've seen once or twice recently. It might be instructive to run setup while using sysinternals' filemon or process monitor (http://technet.microsoft.com/en-gb/sysinternals/bb545046.aspx) and see what was the last file (or the last few files) it tried to access before it crashed. cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/