Stensal™ SDK

Retrofit C/C++ code with quasi-memory-safety

Free for open source projects

Improve the learning experience with C/C++

  • No more cryptic segmentation faults
  • No more hidden data corruption

If you have unexpected behavior in your C/C++ code, start now

Features our users love

The informative messages for the following illegal memory accesses facilitate the understanding of C/C++'s memory model and provide a guide for fixing bugs
  • Out-of-bounds array access
  • Use-after-free
  • Double free
  • Constant data corruption

Real world applications have illegal memory accesses too

  1. Build with the Stensal SDK :
  2. Deploy and Use
  3. Collect

Comparision with other memory error finding tools

Stensal SDK Address Sanitizer* Valgrind**
Detecting memory access violations
Out-of-bounds access of stack-allocated array +++ + -
Out-of-bounds access of heap-allocated array +++ + +
Out-of-bounds access of global array +++ - -
Null (and uninitialized) pointer dereference +++ +++ +++
Use-after-free (stack-allocated) ++ - -
Use-after-free (heap-allocated) ++ - +
Double free ++ + +
Error Reporting
Report the cause +++ + +
Report source location +++ + +
Report backtrace +++ + +
Linking type supported
Static linking
Dynamic linking

+++always, ++very high probability, +most times, -never, and ✔ supported
* clang-7.0.0; ** valgrind-3.10