-
Notifications
You must be signed in to change notification settings - Fork 38.7k
ci: Fuzz with -ftrivial-auto-var-init=pattern #22841
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
See also google/oss-fuzz#5879 |
|
Concept ACK configure: error: unrecognized option: `-ftrivial-auto-var-init=pattern' |
222297f to
98590df
Compare
98590df to
fa0a5fa
Compare
Fixed |
|
This would catch the bug fixed in commit 3737126 . (Memory sanitizers also do that, but there shouldn't be any risk in making our asan config catch it as well.) |
|
Interesting. I wrote a tiny section about the
Concept ACK on running the option on its own in a CI task, for IIUC that would avoid the potential drawbacks. |
|
I don't think those tradeoffs are relevant to the discussion here. |
I thought the information could be interesting for reviewers interested to learn more. |
|
Ah yes, for general background information on the topic that serves as a good starting point. |
|
cr ACK fa0a5fa |
This makes memory bugs deterministic.
-ftrivial-auto-var-init=patternis incompatible with other memory sanitizers (like valgrind and msan), but that is irrelevant here, because the address sanitizer in this fuzz CI config is already incompatible with them.-ftrivial-auto-var-init=patterngoes well with-fsanitize=booland-fsanitize=enum, but those are already enabled via-fsanitize=undefined. See https://clang.llvm.org/docs/UndefinedBehaviorSanitizer.html#available-checks