DynamoRIO / DynamoRIO/drmemory

remove libc from the error report blacklist

Open
#1,684 0 comments 0 reactions 1 assignee Claimed by @zhaoqin View on GitHub
Component-HandleLeak Type-Feature
Dominant language
C
Stars
2.7k
Forks
290
PR merge metrics
No merged PRs in 30d

Description

We should probably consider dynamic libc to be part of the app, rather than a system library, wrt the error report blacklist. We have seen some handle leak callstacks that should be reported rather than marked as "potential" due to several libc frames. We'll need to evaluate on big apps like Chrome whether there is any downside to this proposal.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.