Closed
Bug 1649062
Opened 4 years ago
Closed 4 years ago
Disable the crash reporter for debug fuzzing build
Categories
(Core :: Fuzzing, enhancement)
Tracking
()
RESOLVED
FIXED
mozilla80
People
(Reporter: decoder, Assigned: decoder)
References
Details
Attachments
(1 file)
We currently have a non-ASan debug fuzzing browser build that we use both for regular browser fuzzing as well as libFuzzer-based fuzzing. In this build, the crash reporter and symbol stripping are enabled which is why libFuzzer is not providing proper symbols. I tried disabling stripping and various other configuration tweaks but found that they all seem to affect what symbols minidump_stackwalk provides us. Overall we decided that we should entirely disable the crash reporter for this build type and solely rely on the UBSan runtime to report crashes.
Assignee | ||
Comment 1•4 years ago
|
||
Comment 2•4 years ago
|
||
Once this lands Fuzzfetch will need to be updated to support downloading crashreporter-symbols.zip only for prior builds.
Pushed by choller@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/d213a461c017 Disable the crash reporter in debug fuzzing builds. r=truber,tsmith
Comment 4•4 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 4 years ago
status-firefox80:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla80
Updated•4 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•