Diff Detail
Event Timeline
include/sanitizer/msan_interface.h | ||
---|---|---|
96 |
|
include/sanitizer/msan_interface.h | ||
---|---|---|
96 | This only really matters for functions the would be called from the user code. The idea is that even if some memory is "const", we can mark it as uninitialized or not. The name starts with __sanitizer because it may be implemented in other sanitizers, too. Maybe in the future. ASan can be taught to detect use-after-dtor too, for example, but with some false positives. |
test/msan/dtor-member.cc | ||
---|---|---|
10 | Please add run lines without (a) compiler flag and (b) runtime flag. | |
23 | If we don't crash on the next line (in the negative test), there will be a second destructor call at the function exit, which invokes undefined behavior. Let's change the code to smth like this: unsigned long buf[1]; |
LGTM
lib/msan/msan_interceptors.cc | ||
---|---|---|
1011 | FYI, this tag affects the wording of MSan reports. We may want to introduce a new tag, specifically for use-after-dtor. Not in this commit. | |
test/msan/dtor-member.cc | ||
12 | Could just call it "CHECK-NO" and save one line of code. | |
19 | I don't think this include is needed. | |
37 | "interfere" |
test/msan/dtor-member.cc | ||
---|---|---|
20 | needed for main- can't have void main function. may rename as add more test cases. |
Make it "const volatile *".