Skip to content

Latest commit

 

History

History
26 lines (20 loc) · 1002 Bytes

report_identification.md

File metadata and controls

26 lines (20 loc) · 1002 Bytes

Analyzer report identification

Unique report identifiers are required to compare analysis results. If the analyzers (Clang Static Analyzer, Clang Tidy) do not generate a unique report identifier, CodeChecker tries to generate one.

It is recommended to use the identifier generated by the analyzers because they can include the semantic context of the result better into the unique id.

Experimental context-free hash generation method

This method is used for Clang Tidy reports. The current hash generation algorithm in CodeChecker uses this information to generate the unique id. NOTE: As the main diagnostic section the last element from the bug path is used!

Unique id content:

  • file_name from the main diag section.
  • checker message
  • line content from the source file if can be read up
  • column numbers from the main diag section
  • whitespaces are removed from the source lines used for hash generation to make the hash independent of the indentation