I did this once while graphing the actual calls made. I did a moving 1/10th second window of all the calls and used that to generate successive graphs with the intention of making a movie of my program's call graph and how it changed over time. Perhaps it was just the dumb way I was using GraphViz but I found that because each frame was its own .dot file, the shape of the graph could be radically different and it didn't move nicely.The video wasn't terribly nice to view. Added: I also remember running out of memory because the size of my graphs produced large GIFs and GD seemed to want to host the entire movie in memory while constructing it. Maybe all this would have been easier if I'd been mapping just static call graphs - I was mapping the real deal.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
