Open derekbruening opened 9 years ago
From bruen...@google.com on June 18, 2012 22:09:44
xref issue #828 for heap usage callstacks which should probably remain post-processed for app execution performance reasons.
for leaks we can do online symbolization and leak reporting. that requires sharing the error reporting and suppressing logic in report.c.
Original issue: http://code.google.com/p/drmemory/issues/detail?id=926
From bruen...@google.com on February 17, 2013 08:25:32
Blocking: drmemory:180
From bruen...@google.com on June 18, 2012 22:09:44
xref issue #828 for heap usage callstacks which should probably remain post-processed for app execution performance reasons.
for leaks we can do online symbolization and leak reporting. that requires sharing the error reporting and suppressing logic in report.c.
Original issue: http://code.google.com/p/drmemory/issues/detail?id=926