forked from xiw/stack
-
Notifications
You must be signed in to change notification settings - Fork 0
A static checker for identifying unstable code.
License
wfchandler/stack
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
See INSTALL for build instructions. Make sure STACK binaries are in the PATH. Preparation ----------- STACK works on LLVM bitcode. To analyze a software project, the first step is to generate LLVM bitcode. STACK provides a script called `stack-build`, which both calls gcc (or g++) and in parallel uses Clang to obtain LLVM bitcode from your source code, stored in .ll files. For example: $ cd /path/to/your/project $ stack-build ./configure $ stack-build make or if analyzing a project that is configured using CMake: $ cd /path/to/your/project $ stack-build cmake $ stack-build make Unstable code checker --------------------- To find unstable code that can be eliminated due to undefined behavior, simply run the following command in the project directory after building LLVM bitcode: $ poptck You can find bug reports in `pstack.txt`, in the YAML format. Here's one example: bug: anti-simplify model: | %tobool = icmp ne i8* %p, null, !dbg !14 --> true stack: - p.c:4:0 ncore: 1 core: - p.c:3:0 - null pointer dereference This means the null pointer check at line 4 ("stack:") may be simplified into true ("model:") due to the pointer dereference at line 3 ("core:"). Contact ------- If you find any bugs in STACK, feel free to contact us: you can send us email at [email protected].
About
A static checker for identifying unstable code.
Resources
License
Stars
Watchers
Forks
Releases
No releases published
Packages 0
No packages published
Languages
- C++ 54.4%
- Python 42.9%
- C 1.5%
- Other 1.2%