Closed Bug 1680837 Opened 5 years ago Closed 5 years ago

TSan fuzzing build fails to start

Categories

(Core :: Fuzzing, defect)

defect

Tracking

()

RESOLVED FIXED
85 Branch
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

Can you please bisect this?

Flags: needinfo?(twsmith)
Flags: needinfo?(twsmith)
Regressed by: 1660340
Has Regression Range: --- → yes

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

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.

Assignee: nobody → choller
Status: NEW → ASSIGNED
Pushed by choller@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/46df9a612fb1 Fix libFuzzer gyp flags for nICEr. r=dmajor
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → 85 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: