DynamoRIO/drmemory

track alloc counts per callstack for leak diagnosis

Open

#173 opened on Nov 28, 2014

View on GitHub
 (1 comment) (0 reactions) (0 assignees)C (289 forks)auto 404
MigratedPriority-LowType-Featurehelp wanted

Repository metrics

Stars
 (2,727 stars)
PR merge metrics
 (PR metrics pending)

Description

From derek.br...@gmail.com on December 10, 2010 17:58:15

PR 514043

for analyzing leaks, reporting the count of allocations from that callstack and the ordinals of the ones that leaked would be useful

then you'd know "ok it's the 53rd instance here that leaked, so it's on some rare path, and from the timetamp (PR 465163) it happened late in the run"

this case includes adding the timestamp to leaks that was added to other errors in PR 465163. we'll have to add it to all stored callstacks which will occupy some space, so we may want it under a runtime option

Original issue: http://code.google.com/p/drmemory/issues/detail?id=173

Contributor guide

Research direction
Examine the memory allocation tracking mechanisms in DrMemory, understand how callstacks are stored, and implement a runtime option to record allocation counts per callstack for leak diagnosis.
Tech stack
c
Domain
backendtooling
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Cmemory managementdebugging concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20