X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org From: "Dave Korn" To: References: <20080527140538.GD32147@ednor.casa.cgf.cx> 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: Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.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/