This revision was automatically updated to reflect the committed changes.
Closed by commit rL318030: [analyzer] Document the issue hash debugging
facility (authored by xazax).
Changed prior to commit:
https://reviews.llvm.org/D39543?vs=121290&id=122630#toc
Repository:
rL LLVM
https://review
NoQ accepted this revision.
NoQ added a comment.
This revision is now accepted and ready to land.
> these kinds of tasks should have the same level of attention as others
Dunno really. I'm not sure anybody actually reads that doc instead of
accidentally finding the checker code by debugging how
xazax.hun added inline comments.
Comment at: docs/analyzer/DebugChecks.rst:255
+ int x = 1;
+ clang_analyzer_hashDump(x); // Hashed string of x on stderr.
+}
NoQ wrote:
> Unlike `printState` and like all other functions, your function doesn't dump
xazax.hun updated this revision to Diff 121290.
xazax.hun marked 2 inline comments as done.
https://reviews.llvm.org/D39543
Files:
docs/analyzer/DebugChecks.rst
Index: docs/analyzer/DebugChecks.rst
===
--- docs/analyzer/DebugChec
NoQ added a comment.
Yup, thanks!
Comment at: docs/analyzer/DebugChecks.rst:255
+ int x = 1;
+ clang_analyzer_hashDump(x); // Hashed string of x on stderr.
+}
Unlike `printState` and like all other functions, your function doesn't dump to
plain s
jklaehn added inline comments.
Comment at: docs/analyzer/DebugChecks.rst:247
+
+ The analyzer can generate a hash to identify repots. To debug what
information
+ is used to calculate this hash it is possible to dump the hashed string to
typo `reports`?
Repos
xazax.hun created this revision.
Herald added subscribers: szepet, baloghadamsoftware, whisperity.
Add documentation to the recently added issue hash dumping function.
Repository:
rL LLVM
https://reviews.llvm.org/D39543
Files:
docs/analyzer/DebugChecks.rst
Index: docs/analyzer/DebugCheck
