X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Sun, 19 Oct 2008 11:33:22 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: cygwin bash crashes on 64bit Windows Server 2008 Message-ID: <20081019153322.GA23774@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <081019081235 DOT ZM26426 AT adobe DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <081019081235.ZM26426@adobe.com> User-Agent: Mutt/1.5.16 (2007-06-09) 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 On Sun, Oct 19, 2008 at 08:12:35AM -0700, Freddy Jensen wrote: >Has anyone tried cygwin on a 64-bit Windows Server 2008 system? > >After I install it, bash crashes on startup like this: > >Exception: STATUS_ACCESS_VIOLATION at eip=0043AE30 >eax=00000000 ebx=00000000 ecx=61106EC8 edx=00000000 esi=611021A0 edi=0045A060 >ebp=0027CCB8 esp=0027C67C program=C:\cygwin\bin\sh.exe, pid 2244, thread main >cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B >Stack trace: >Frame Function Args >0027CCB8 0043AE30 (00000002, 6116C8C0, 013C0090, 00000000) >0027CD68 610060D8 (00000000, 0027CDA0, 61005450, 0027CDA0) >61005450 61004416 (0000009C, A02404C7, E8611021, FFFFFF48) > 3 [main] sh 2244 _cygtls::handle_exceptions: Error while dumping state (probably corrupted stack) > > > >Has anyone found a work-around? Maybe, but you would have to start here first: >Problem reports: http://cygwin.com/problems.html If you really wanted to find one. 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/