In message <Pine.NEB.3.96L.1050208164554.18460A-100000_at_fledge.watson.org>, Robert Watson writes: >That and a lot of hand-crafting and cleanup. The first thing you find out >when trying to apply cflow and graphviz to the kernel in order to generate >a call flow diagram is that there's a lot of "stuff" and the type of >picture you want is as much a product of how you plan to use the picture >as the source you base it on. The tcl/tk scripts I've done grabs everything, then you tell it incrementally what functions to "loose", things like "__.*" and "mtx.*" is a good start. You can also add lines which are missing. Since the script have no idea where calls through pointers go it adds a pseudofunction with a star prefixed, and it's your own responsibility to link these up. It's not great, but it works. It would be neat if somebody write code to use the GUI bits of Tk so that you could point and click more etc. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk_at_FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.Received on Tue Feb 08 2005 - 15:57:03 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:27 UTC