Process Debugging questions
Alexander Leidinger
Alexander at Leidinger.net
Tue Nov 21 14:47:22 UTC 2006
Quoting Robert Watson <rwatson at FreeBSD.org> (from Tue, 21 Nov 2006
14:21:59 +0000 (GMT)):
>
> On Tue, 21 Nov 2006, Alexander Leidinger wrote:
>
>> Quoting Robert Watson <rwatson at 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
With DTrace we have access to a lot of stuff. I think this is only a
case of writting the right dtrace script (intercepting
malloc/free/sbrk/mmap/... should allow for more sophisticated output).
Bye,
Alexander.
--
http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7
http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137
More information about the freebsd-hackers
mailing list