Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
X-Originating-IP: [203.26.31.20]
From: "Gareth Pearce" <tilps AT hotmail DOT com>
To: <cygwin AT cygwin DOT com>
Subject: valgrind
Date: Wed, 1 Jan 2003 20:28:30 +1100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Message-ID: <OE59oGdKO8FNpyLAPDV00000293@hotmail.com>
X-OriginalArrivalTime: 01 Jan 2003 09:28:32.0447 (UTC) FILETIME=[26C594F0:01C2B178]

Hi,

Has anyone atempted to port valgrind to cygwin?
I thought it was something that would be good to do, but its looking like
quite a big job, given that its tied so strongly to the linux kernel.  I
could keep ripping it to bits until it compiles - but I am guessing the end
product will be useless.
Is it feasible at all given cygwin not actually being an OS? -- would i
really effectively need to port it to native windows?

Gareth

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/