Log In
Log In

Posts

Stay up to date with Boost and the C++ ecosystem with the latest news, videos, resources, and user-created content.

Filter

All

Latest Posts

  • Test 2
    AddressSanitizer finds memory bugs on OSes. Detects use‑after‑free and leaks. LeakSanitizer adds leak detection. UBSan MSan TSan cover UB uninit reads races. Enable with -fsanitize or B2. Valgrind checks memory on Linux. Both integrate into CI pipelines.
    News
  • Fuzz testing
    Fuzz testing is described as a technique that injects random data into software functions to expose crashes, memory leaks, and undefined behavior, especially in code handling untrusted input. A fuzzing engine repeatedly runs the target code with varied inputs, instrumenting it to collect coverage information that guides the generation of further samples, most of which are malformed. Crashes and sanitizer violations are monitored, making the approach valuable for libraries that parse or decode network data, such as Boost.Json, Boost.URL, and Boost.Mysql. Unit tests are still required, as they verify expected results, while fuzzing complements them by focusing on stability rather than correctness. LibFuzzer is recommended as the default engine because it is coverage‑guided, evolutionary, and bundled with clang, requiring only the addition of ‑fsanitize=fuzzer flags during compilation.
    Blog

Create an account

Advance your career, learn from experts, and help shape the future of Boost and C++.

Sign Up Now