X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.3 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <AANLkTim+hU+Cg6_J83B_h9VHsL8wiC4Xh7TbcwzjSjkW@mail.gmail.com>
References: <AANLkTim+hU+Cg6_J83B_h9VHsL8wiC4Xh7TbcwzjSjkW AT mail DOT gmail DOT com>
Date: Mon, 13 Sep 2010 15:52:55 -0300
Message-ID: <AANLkTim6mZiJOzmM=CungVZnhWUdvADbJVsr+yjPofd8@mail.gmail.com>
Subject: Re: Cygwin instabilities
From: Ramiro Polla <ramiro DOT polla AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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 Mon, Sep 13, 2010 at 10:19 AM, Al <oss DOT elmar AT googlemail DOT com> wrote:
> Others report that they don't use Cygwin because of instablilities,
> especially in the server context.

I've also been having "instabilities" in my "server context" (Windows
Server 2008 R2), but I have a few more concrete details:

I had 1.7.5 installed, and built gcc-3.4.6, gcc-4.2.4, and gcc-4.4.4
to use on a continuous integration test box. All went relatively fine.
I updated to 1.7.7 and kept using the toolchains built with 1.7.5. I
got that some of the build cycles would hang in "make" (in gcc.exe or
tr.exe actually) with "Bad address". The process would still appear in
pstree with a * and I had to "/usr/bin/kill -W" it. Since it seemed to
happen randomly, it wasn't easily reproducible, so I don't how or what
exactly to debug. Is there any way to try and trap that error? I could
also try to log everything with strace but I'm afraid that would
produce tons of data (the builds could run for hours before such error
occurred).

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple