Date: Tue, 21 Nov 2006 14:21:59 +0000 (GMT) From: Robert Watson <rwatson@FreeBSD.org> To: Alexander Leidinger <Alexander@Leidinger.net> Cc: trowa-4 <trowa-4@yahoo.com.tw>, Dag-Erling =?utf-8?b?U23DuHJncmF2?= <des@des.no>, Jeremie Le Hen <jeremie@le-hen.org>, freebsd-hackers@FreeBSD.org Subject: Re: Process Debugging questions Message-ID: <20061121142005.T63599@fledge.watson.org> In-Reply-To: <20061121150941.wlwmfw8u0w0c444k@webmail.leidinger.net> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 21 Nov 2006, Alexander Leidinger wrote: > Quoting Robert Watson <rwatson@FreeBSD.org> (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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061121142005.T63599>