X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Thu, 7 May 2009 15:52:58 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Bug to setup Cygwin on Windows Server 2008 64bits Message-ID: <20090507135258.GB21324@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <23422628 DOT post AT talk DOT nabble DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <23422628.post@talk.nabble.com> User-Agent: Mutt/1.5.19 (2009-02-20) 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 May 7 01:48, Kyeto wrote: > > Hi, > > I have already installed Cygwin on several computers on 32 bits. > But now, i need to setup it on my Windows Enterprise Server 2008 64bits. > > During the setup, there is no error. > But when i lunch Cygwin, i have some exception which shutdown cygwin. (look > the screenshoot) > http://www.nabble.com/file/p23422628/Picture%2B2.png > > And in the file bash.exe.stackdump : > > Exception: STATUS_ACCESS_VIOLATION at eip=0043AF00 > eax=00000000 ebx=00000000 ecx=61106EC8 edx=00000000 esi=611021A0 > edi=0045A190 > ebp=0027CC98 esp=0027C65C program=C:\cygwin\bin\bash.exe, pid 3396, thread > main > cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B > Stack trace: > Frame Function Args > 0027CC98 0043AF00 (00000001, 011601B0, 01160090, 61010E8C) > 0027CD68 610060D8 (00000000, 0027CDA0, 61005450, 0027CDA0) > 61005450 61004416 (0000009C, A02404C7, E8611021, FFFFFF48) > 82763 [main] bash 3396 _cygtls::handle_exceptions: Exception: > STATUS_ACCESS_VIOLATION > 85226 [main] bash 3396 _cygtls::handle_exceptions: Error while dumping > state (probably corrupted stack) > > How can i resolv this problem ? I have search on different forum but i don't > find any answer. This could be an issue with Terminal Server. If you installed TS on that machine, as a temporary workaround, switch off DEP. For the mid term we have a tool called peflags/peflagsall (in the rebase package) which allows to set the TS-awareness flag in executables. This will get rid of the problem (just use it from ash, which isn't affected by the problem for some reason). For the long term we will get a new gcc-4 at one point which sets the TS-awareness flag for newly created executables automatically. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/