awesome-lockpicking
Cppcheck
| awesome-lockpicking | Cppcheck | |
|---|---|---|
| 1 | 11 | |
| 1,303 | 5,454 | |
| - | - | |
| 0.0 | 9.9 | |
| almost 2 years ago | 3 days ago | |
| C++ | ||
| Creative Commons Zero v1.0 Universal | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
awesome-lockpicking
-
Awesome Penetration Testing
See awesome-lockpicking.
Cppcheck
-
Configuring Cppcheck, Cpplint, and JSON Lint
I dedicated Sunday morning to going over the documentation of the linters we use in the project. The goal was to understand all options and use them in the best way for our project. Seeing their manuals side by side was nice because even very similar things are solved differently. Cppcheck is the most configurable and best documented; JSON Lint lies at the other end.
- Cppcheck/Releasenotes.txt
-
Enforcing Memory Safety?
Using infer, someone else exploited null-dereference checks to introduce simple affine types in C++. Cppcheck also checks for null-dereferences. Unfortunately, that approach means that borrow-counting references have a larger sizeof than non-borrow counting references, so optimizing the count away potentially changes the semantics of a program which introduces a whole new way of writing subtly wrong code.
-
Check out my tasks.json for C++ of VScode
Also check out (cppcheck)[https://github.com/danmar/cppcheck] if you want more static analysis
-
What are the must-have tools for any C++ developer?
My browser refuses to open that link. This is better: https://github.com/danmar/cppcheck
-
Awesome Penetration Testing
cppcheck - Extensible C/C++ static analyzer focused on finding bugs.
-
C/C++ pre-commit hooks for static analyzers and linters
and five C/C++ static code analyzers: * clang-tidy * oclint * cppcheck * cpplint (recently added!) * include-what-you-use (recently added!)
-
Caught signal 11 (SIGSEGV) and signal 6 (SIGABRT)
Start by feeding your codebase to a static analysis tool like cppcheck, to rule out obvious bound-checking mistakes in it.
- How to detect stack corruption in embedded c??
-
Why static analysis on C projects is not widespread already?
Cppcheck is free. I've previously used it with a C++ project.
What are some alternatives?
LOIC - Deprecated - Low Orbit Ion Cannon - An open source network stress tool, written in C#. Based on Praetox's LOIC project. USE ON YOUR OWN RISK. WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES. IF YOU GET V& IT IS YOUR FAULT.
cpplint - Static code checker for C++
gcc-poison - gcc-poison
stb - stb single-file public domain libraries for C/C++
cmake-lint - Fork of https://github.com/richq/cmake-lint to continue maintenance
American Fuzzy Lop - american fuzzy lop - a security-oriented fuzzer
c-smart-pointers - Smart pointers for the (GNU) C programming language
ZXing - ZXing ("Zebra Crossing") barcode scanning library for Java, Android
C++ Format - A modern formatting library
RE2 - RE2 is a fast, safe, thread-friendly alternative to backtracking regular expression engines like those used in PCRE, Perl, and Python. It is a C++ library.
Better Enums - C++ compile-time enum to string, iteration, in a single header file
Klib - A standalone and lightweight C library