Hello everyone,
I've been working on a project of mine for a little while now, called Aesalon. It is now beginning to become "stable", and I thought someone here might be interested in it.
Rather than type it all out again, I will instead quote the RELEASE file for Aesalon . . .
Aesalon is hosted by gitorious, if you're interested. The full release notes include compilation instructions, if you are interested.In one sentence, Aesalon is a tool to visualize, in real-time, the dynamically-allocated memory that another program has allocated. Aesalon currently only functions on x86_64 GNU/Linux systems, though it would be easily ported to x86 GNU/Linux, BSD, or any other POSIX-compliant system. Why hasn't it been ported yet, you ask? Well, because I'm lazy, and because my computer doesn't have anything other than x86_64 GNU/Linux distros installed.
Aesalon is useful for memory-leak tracking (and it will be even more useful in the near future), and can also be used for profiling/optimization. Currently, Aesalon displays the memory data in two separate ways: a simple graph of active blocks over time, and other, what I term a "density" visualization, which is address space over time. Aesalon draws rectangles to denote blocks: the taller the block, the larger it is, the wider, the longer it was allocated for. This is the most useful visualization of the two. I'm also planning a few more, such as the ability to show which scope had the most activity, etc. However, that's for next week . . .
Again, I'm mainly throwing this out here in case anyone is interested. Aesalon, as it stands, is mainly incomplete (there's a lot of inefficiencies in it, far too many linear-time operations for my liking . . .), but I thought I'd try and write this project in the spirit of FOSS: "release early, release often". To quote from the release notes, "[t]here's a reason this is tagged version 0.1.0 . . .".
I'd attach a precompiled binary, but the maximum upload size CBoard supports is about 500KB, and the .tar.gz version of Aesalon is 2.4MB. Unfortunately, this means you'll have to compile it yourself if you're interested . . . sorry about that.
Let me know what you think. Criticism welcomed.