umnsec / cheq Goto Github PK

Would you like to wrap any pointers with the class template “std::unique_ptr”?

• Would you like to add more error handling for return values from calls of a function like strdup()?
• Can your analysis tool point similar source code places out for further software development considerations?

I would find it helpful if a few examples will be presented here for the diagnostic displays which are supported by your source code analysis tool.
How do you think about to clarify the provided information?

I would like to point out that identifiers like “_ANALYZER_GLOBAL_H” and “_CALL_GRAPH_H” do eventually not fit to the expected naming convention of the C++ language standard.
Would you like to adjust your selection for unique names?

Hi,

I'm trying to use your tool to do some security checks. I can successfully run the tool by following instructions. However, after running the tool, I can only get the details shown on my terminal, which is similar to the below messages. So I am wondering how can I get the final bug report?

Total 18074 file(s)
[CallGraph] Initializing 18074 modules 
[CallGraph / 1] [1 / 18074] [../../bc/arch/x86/kvm/i8259.bc]

[CallGraph / 1] [2 / 18074] [../../bc/arch/x86/kvm/pmu.bc]

[CallGraph / 1] [3 / 18074] [../../bc/arch/x86/kvm/pmu_amd.bc]

[CallGraph / 1] [4 / 18074] [../../bc/arch/x86/kvm/mmu.bc]

[CallGraph / 1] [5 / 18074] [../../bc/arch/x86/kvm/irq.bc]

[CallGraph / 1] [6 / 18074] [../../bc/arch/x86/kvm/debugfs.bc]

[CallGraph / 1] [7 / 18074] [../../bc/arch/x86/kvm/ioapic.bc]
...

I have accidentally noticed a few typos.

• https://github.com/umnsec/cheq/blob/9360f7d6c2e35ccaacbb2ac17705587beb43adce/README.md#run-the-cheq-analyzer

• cheq/analyzer/src/lib/Analyzer.cc

  Line 3 in 5138223

  // This file implemets the analysis framework. It calls the pass for

Would you like to adjust affected places?