Skip to content

Recommendations for which sanitizers to enable #41

@springmeyer

Description

@springmeyer

As time passes, the g++/clang++ gain more new sanitizers, existing ones get better, and some get ported to new platforms (e.g. recently leak support was added to OS X in clang++ 5).

Similar to #37 for warnings, This ticket can serve as a central place to start documenting a recommended list of sanitizer flags to use. I intend this to be a quick, opinionated reference to check before you would dive deeper into docs like https://clang.llvm.org/docs/UndefinedBehaviorSanitizer.html.

The relevant questions I see are:

  • 🍇 Which sanitizers should we always test with?
  • 🍊 Which additional flags or environment variables should we use?
  • 🍏 Which additional flags should be used when testing the sanitizers on CI systems?
  • 🍎 Which additional flags should be used when building sanitized binaries for live testing?

Refs:

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions