X-Spam-Check-By: sourceware.org Date: Thu, 24 Aug 2006 12:37:13 -0400 (EDT) From: Igor Peshansky Reply-To: cygwin AT cygwin DOT com To: Eric Cadwell cc: cygwin AT cygwin DOT com Subject: Re: setup errors with access violation In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk 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 On Thu, 24 Aug 2006, Eric Cadwell wrote: > We are getting setup errors on some Windows 2003 servers. Some are fine, > some have errors. Any ideas? > > Here's the setup log.... > 2006/08/23 13:57:47 Starting cygwin install, version 2.548 Try the latest snapshot (2.551, I believe). In fact, 2.548 was not released as a snapshot -- is that a self-built version? > 2006/08/23 13:57:47 io_stream_cygfile: fopen(/etc/setup/last-action) failed 2 No such file or directory > 2006/08/23 13:57:47 io_stream_cygfile: fopen(/etc/setup/last-connection) failed 2 No such file or directory > 2006/08/23 13:57:47 io_stream_cygfile: fopen(/etc/setup/last-cache) failed 2 No such file or directory Those are normal, and should happen on first install. > 2006/08/23 13:57:47 Current Directory: tmp\install > 2006/08/23 13:57:47 > Command Line Options: Aww, you've snipped the most useful part... > Ending cygwin install > > And the dump... > Application exception occurred: > App: C:\download\setup.exe (pid=384) > When: 8/23/2006 @ 13:20:19.442 > Exception number: c0000005 (access violation) > > *----> System Information <----* > Computer Name: NUNYA > User Name: admin > Terminal Session Id: 1 > Number of Processors: 2 > Processor Type: x86 Family 15 Model 6 Stepping 2 > Windows Version: 5.2 > Current Build: 3790 > Service Pack: 1 > Current Type: Multiprocessor Free If you have a locally built version, please build it with debugging, run setup in gdb, and provide a stack trace of the exception. Otherwise, try the latest snapshot, and provide more information about exactly when setup crashes (i.e., which screen, what steps you've completed, which user runs setup -- local, domain, admin, etc). Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!) |,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte." "But no -- you are no fool; you call yourself a fool, there's proof enough in that!" -- Rostand, "Cyrano de Bergerac" -- 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/