TSan fuzzing build fails to start
Categories
(Core :: Fuzzing, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr78 | --- | unaffected |
firefox83 | --- | wontfix |
firefox84 | --- | wontfix |
firefox85 | --- | fixed |
People
(Reporter: tsmith, Assigned: decoder)
References
(Regression)
Details
(Keywords: crash, regression)
Attachments
(1 file)
The TSan fuzzing builds crash on start up with this message:
-fsanitize-coverage=trace-pc-guard is no longer supported by libFuzzer.
Please either migrate to a compiler that supports -fsanitize=fuzzer
or use an older version of libFuzzer
Reporter | ||
Comment 2•5 years ago
|
||
The first failing build is: https://hg.mozilla.org/mozilla-central/rev/30a8286a26edd6f40ec6ea10e37b9a41ea2c7aaa
So my guess is bug 1660340.
Updated•5 years ago
|
It would be interesting to know why we're passing trace-pc-guard
in the first place, in other words why don't we take the early returns for "using tsan" or "clang >= 6" here: https://searchfox.org/mozilla-central/rev/1843375acbbca68127713e402be222350ac99301/build/moz.configure/toolchain.configure#2749,2758
Assignee | ||
Comment 4•5 years ago
|
||
The gyp flag logic in nICEr is supposed to ensure that the code is instrumented
for libFuzzer because we have a related fuzzing target. However, libFuzzer
instrumentation must be completely disabled for TSan due to incompatibility.
The current logic fails in doing so and incorrectly falls back to legacy
trace-pc instrumentation causing the TSan fuzzing build to fail on startup.
Updated•5 years ago
|
Comment 6•5 years ago
|
||
bugherder |
Updated•5 years ago
|
Updated•5 years ago
|
Description
•