DynamoRIO / DynamoRIO/drmemory
remove libc from the error report blacklist
Open
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
Assessment
This issue has not been assessed yet.