Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262398AbVD2GNy (ORCPT ); Fri, 29 Apr 2005 02:13:54 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262397AbVD2GNy (ORCPT ); Fri, 29 Apr 2005 02:13:54 -0400 Received: from ylpvm12-ext.prodigy.net ([207.115.57.43]:44940 "EHLO ylpvm12.prodigy.net") by vger.kernel.org with ESMTP id S262398AbVD2GM6 (ORCPT ); Fri, 29 Apr 2005 02:12:58 -0400 X-ORBL: [67.124.119.21] Date: Thu, 28 Apr 2005 23:12:54 -0700 From: Chris Wedgwood To: Gilles Pokam Cc: linux-kernel@vger.kernel.org Subject: Re: Kernel memory Message-ID: <20050429061254.GB12654@taniwha.stupidest.org> References: <20050429030313.GA10344@taniwha.stupidest.org> <20050429054351.GA12654@taniwha.stupidest.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 543 Lines: 14 On Thu, Apr 28, 2005 at 10:48:31PM -0700, Gilles Pokam wrote: > Can you be more explicit ? why can't you have the parent process of whatever your tracing mess with /dev/kmem or whatever so you don't have to frob the original binary? i guess it's not really clear to me what you're doing entirely - 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/