google / google/sanitizers

MSan use-after-destroy does not poison objects with implicit destructors

Open
#596 7 comments 0 reactions 1 assignee Assigned to @eugenis View on GitHub
ProjectMemorySanitizer
Dominant language
C
Stars
12.5k
Forks
1.1k
PR merge metrics
No merged PRs in 30d

Description

During code generation, no destructor exists to emit a destructor body for, so no members are poisoned. In order to do, a destructor must be generated for this object.

The creation of implicit destructors occurs during semantic analysis (clang/sema/). However, this step has no access to command line options.

Either semantic analysis must have access to the command line options, to check for msan and emit the required destructor, or another approach must be taken.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.