Skip to content
This repository has been archived by the owner on Jul 3, 2024. It is now read-only.

Smarter uniqueing for warnings #84

Open
Xazax-hun opened this issue Dec 27, 2019 · 0 comments
Open

Smarter uniqueing for warnings #84

Xazax-hun opened this issue Dec 27, 2019 · 0 comments

Comments

@Xazax-hun
Copy link
Collaborator

If we dereference a dangling pointer (pointee went out of scope) multiple times we will get multiple warnings. We unique warnings based on the report location. But in fact, all the errors were the same. So maybe we should have emitted only one warning per pointee out of scope. So maybe, for some warnings, we should use the notes as a uniqueing location instead of the actual warning. The clang static analyzer does something similar for leaks, instead of reporting them on every path, it reports leaks only once per allocation site.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant