-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[BUG] Fuzzing integration build (Linux) - invalid argument '-fsanitize=address' not allowed with '-fsanitize=thread' #25959
Comments
it looks to me like we should probably update our documentation. |
oh .. typo in variant ... should not be asan, should be fuzzer. Will create a PR. |
Fixed ... als tried it to see it runs ... it does and crashes right away. We may need to fix some things ... |
It seems fuzzing was not run for a long time, so actual prerequisites are not set in main. |
DataProvider fixed in #25968 |
Reproduction steps
Following the libfuzzer command for linux listed under 'Fuzzing integration' instructions here:
./scripts/run_in_build_env.sh "./scripts/build/build_examples.py --target linux-x64-all-clusters-no-ble-asan-libfuzzer-clang build"
On a fresh linux environment (Docker container on Windows host) results in the error:
Bug prevalence
Whenever I do this
GitHub hash of the SDK that was being used
d81d4e3
Platform
windows
Platform Version(s)
No response
Anything else?
I believe this is because the following line enables tsan (while the sample command manually includes
-asan-
):connectedhomeip/scripts/build/build/targets.py
Line 143 in d81d4e3
Additionally, if I bypass this manually (by updating targets.py to also default to asan) it seems to only produce a standard (non-libfuzzer) binary.
(I believe the output binary should be
chip-all-clusters-app-fuzzing
). Executing the binary results in standard all-clusters-app operation, with no libfuzzer output:The text was updated successfully, but these errors were encountered: