This visualization is the result of an adapted visichron.py script (from my chronicle-recorder ‘chroniquery’ bindings) run against the output of a custom DTrace script (using the Mozilla JS providers) on OS X. It’s a proof-of-possibility rather than anything immediately useful. The differences from the last visichron post (using chronicle-recorder as a back-end) are: Node [...]
Also tagged dtrace, lightning, visophyteMy personal laptop rolls amd64-style (rather than i686), and chronicle-recorder’s valgrind component was not working on it (“illegal instruction”). I have done some vendor-branch dancing to get chronicle-recorder’s valgrind sub-directory to use valgrind 3.3.0. A bzr branch of just the valgrind subdirectory (drop-in or build separately and make sure you invoke valgrind from that location) [...]
Also tagged chronicle, chroniquery, visophyteThanks to new and improved time management skills (and a holiday weekend doesn’t hurt), I’ve got a chronicle-recorder visualization going on via chroniquery: Above, we have the visualization run against the ‘fancy’ program seen in the previous chroniquery posts (with one caveat, addressed later). What does it mean? The circular nodes are functions in the [...]
Also tagged chronicle, chroniquery, visophyte