|
From: Bryan M. <om...@br...> - 2006-07-02 15:47:59
|
please see http://www.brainmurders.eclipse.co.uk/omega.html for a complete overview of what this tool can do for you! (We use this heavily at work - feel free to give it a spin...) >From the web page: ================== Omega addresses what I perceive to be one of the few shortfalls of the excellent Valgrind Memcheck Tool - where Memcheck reports the location that a leaked block was allocated, Omega also shows where it was leaked. New in Beta4: ============= Bug fix in circular reference detection. Function wrappers around memcpy(), memmove() and memset(). More robust detection of functions returning values in the accumulator (fixes a false positive). Known Issues: ============= I have a wrapper around main() to detect when to stop tracking - if you are using threads and they don't exit before main() does, there will be problems. I haven't particularly tested this with threads yet - that's targeted for the next beta. Requested Features? =================== I am still toying with the idea of allowing targeted tracking through the use of the suppression system - exclusively report on a specified malloc() call. show hanging pointers at a targeted call to free(). turn on more verbose output for a given memory block. Generate leak reports in some XML format to make machine parsing simple. If you use Omega and think any of these features would be useful or have requests of your own, please let me know. As ever, I would welcome your comments, bug reports and especially any news of success stories. thanks, Bryan "Brain Murders" Meredith |