From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 21 14:22:24 2006 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7506916A47B for ; Tue, 21 Nov 2006 14:22:24 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id E8BF943D5E for ; Tue, 21 Nov 2006 14:21:37 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 351B846E4F; Tue, 21 Nov 2006 09:21:59 -0500 (EST) Date: Tue, 21 Nov 2006 14:21:59 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Alexander Leidinger In-Reply-To: <20061121150941.wlwmfw8u0w0c444k@webmail.leidinger.net> Message-ID: <20061121142005.T63599@fledge.watson.org> References: <571883.4868.qm@web72011.mail.tp2.yahoo.com> <86irhlfvg2.fsf@dwp.des.no> <20061120221026.GC20405@obiwan.tataz.chchile.org> <86d57hjhwu.fsf@dwp.des.no> <20061121115333.N50450@fledge.watson.org> <20061121150941.wlwmfw8u0w0c444k@webmail.leidinger.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: trowa-4 , Dag-Erling =?utf-8?b?U23DuHJncmF2?= , Jeremie Le Hen , freebsd-hackers@FreeBSD.org Subject: Re: Process Debugging questions X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Nov 2006 14:22:24 -0000 On Tue, 21 Nov 2006, Alexander Leidinger wrote: > Quoting Robert Watson (from Tue, 21 Nov 2006 11:55:37 > +0000 (GMT)): > >> Anyone who wants to start looking at a new API should make sure they look >> at ptrace() and procfs across a range of platforms, and also look at Mach >> task ports and what they offer. One of the things we really can't do well >> with ptrace() today is inspect kernel state for a running process -- things >> like the VM layout, etc. We should make sure any next generation system >> allows this, because that feature alone is the reason why I sometimes mount >> procfs. :-) > > Can you please elaborate what features you have in mind which DTrace isn't > able to deliver? /proc/curproc/map Robert N M Watson Computer Laboratory University of Cambridge