Summary: | Massif loses track of memory, incorrect graphs | ||
---|---|---|---|
Product: | [Developer tools] valgrind | Reporter: | Axel Liljencrantz <liljencrantz> |
Component: | massif | Assignee: | Nicholas Nethercote <njn> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | 3.1.0 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Axel Liljencrantz
2006-06-21 15:44:43 UTC
[A general message:] Massif has recently been completely overhauled. Instead of recording space-time usage, it now records space usage at various points during execution, including the peak allocation point. The output format has also changed, and presents more information, more compactly. It's also more robust than the old version. The new version will be Valgrind 3.3.0, which should be released in the next week or two. In the meantime, if you want to try it, please check out the code from the SVN repository (see http://www.valgrind.org/downloads/repository.html for how). [A specific message about this bug:] I'm closing this bug, as the new version should have fixed the problem. Please reopen if it still happens. |