X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
From: "Dave Korn" <dave DOT korn AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
References: <BLU116-W26BA00024BFA1EA385E65FEFBD0 AT phx DOT gbl>   <20080527140538 DOT GD32147 AT ednor DOT casa DOT cgf DOT cx>  <BLU116-W174393FFD0C1D336CF4751EFBD0 AT phx DOT gbl> <BLU116-W24F6A80B5FA753EE5B3E76EFB50 AT phx DOT gbl>
Subject: RE: 1.5.25: Random segfaults in unix tools
Date: Wed, 4 Jun 2008 13:06:08 +0100
Message-ID: <03c901c8c63b$601d1d30$2708a8c0@CAM.ARTIMI.COM>
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <BLU116-W24F6A80B5FA753EE5B3E76EFB50@phx.gbl>
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

Jamie Cole wrote on 04 June 2008 12:56:

> Also we have an identical physical (e.g. non VMWare) machine running the
> same tools and version of Cygwin which does not seg fault. Is it possible
> there is a actually a bug in Cygwin which is causing these problems when
> running on a virtual machine?   

  Uhhh, by definition, if the same piece of software doesn't do /exactly/
the same thing on a virtualised machine as it does on a real machine, it is
the *virtualisation* that is at fault, not the software running under it.

> As virtualisation is a growing technology this could cause problems in
> the future 

  As virtualisation is a growing technology (as opposed to a stable and
mature technology), it still suffers from bugs.

  This is not to say that putting a workaround to support buggy VMs in
cygwin would necessarily be out of the question, as long as it didn't impact
on the far greater number of users running cygwin on real hardware...

    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/