Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • C cmsgemos
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 100
    • Issues 100
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 13
    • Merge requests 13
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • cmsgemonline
  • gem-daq
  • cmsgemos
  • Issues
  • #55

Closed
Open
Created May 02, 2020 by Louis Moureaux@lmoureauDeveloper

Encourage using sanitizers

Summary

GCC and clang come with a set of sanitizers that attempt to find various common mistakes at runtime. Examples include out-of-bounds array indices, dangling pointers, unsafe concurrent access, division by zero... They are enabled using the -fsanitize compiler option; refer to the GCC manual for details. -fsanitize=address alone found several bugs in the various code bases I use.

We should provide instructions how to enable them to encourage their use, and maybe eventually run CI tests with sanitizers enabled.

Assignee
Assign to
Time tracking