Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 21 Oct 2002 20:24:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 21 Oct 2002 20:24:34 -0400 Received: from mnh-1-14.mv.com ([207.22.10.46]:40965 "EHLO ccure.karaya.com") by vger.kernel.org with ESMTP id ; Mon, 21 Oct 2002 20:24:34 -0400 Message-Id: <200210220134.UAA05438@ccure.karaya.com> X-Mailer: exmh version 2.0.2 To: mailing-lists@digitaleric.net cc: linux-kernel@vger.kernel.org Subject: Re: valgrind URL In-Reply-To: Your message of "Mon, 21 Oct 2002 19:48:20 -0400." <200210211948.20840.lkml@digitaleric.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Oct 2002 20:34:51 -0500 From: Jeff Dike Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 606 Lines: 17 lkml@digitaleric.net said: > http://developer.kde.org/~sewardj/ And to bring this thread a bit on-topic (:-), I'm currently engaged in a re-work of UML that will make it a normal enough process that valgrind will just work on it. I, and a number of other people, are expecting all kinds of crap to fall out when we are able to valgrind the kernel. Jeff - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/