CHECK failure: !entry_manager_->global_db_path_.empty() in entry_manager_test_util.cc |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4712983697293312 Fuzzer: libFuzzer_chromeos_usb_bouncer_fuzzer Job Type: libfuzzer_ubsan_chromeos Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: !entry_manager_->global_db_path_.empty() in entry_manager_test_util.cc usb_bouncer::EntryManagerTestUtil::RecreateEntryManager usb_bouncer::EntryManagerTestUtil::EntryManagerTestUtil Sanitizer: undefined (UBSAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_ubsan_chromeos&range=3177391:3177583 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4712983697293312 Issue filed automatically. See https://chromium.googlesource.com/chromiumos/docs/+/master/fuzzing.md#Reproducing-crashes-from-ClusterFuzz for more information.
,
Dec 3
Is there anything special needed in the gyp or ebuild to get line numbers in the stack trace provided by clusterfuzz?
,
Dec 3
Clusterfuzz also didn't add people to CC list. metzman@ can you check why folks in OWNERS file were not added.
,
Dec 3
Allenwebb@ regarding stack traces, can you check if "-g" is being passed to the compilation flags.
,
Dec 4
ClusterFuzz testcase 4712983697293312 appears to be flaky, updating reproducibility label.
,
Dec 4
Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This was caused by a bug in ClusterFuzz that has been fixed. Sorry again for the inconvenience.
,
Dec 4
I cannot reproduce this one locally so I think there is likely a difference in the fuzzer build configuration and the test script. Where I can I see the scripts that run the fuzz targets for clusterfuzz so I can try to track down the difference and reproduce this?
,
Dec 4
This target is likely to fail initialization with an ASAN error for builds after the following CL landed: https://chromium-review.googlesource.com/c/chromiumos/platform2/+/1351244/9 That problem is fixed in: https://chromium-review.googlesource.com/c/chromiumos/overlays/chromiumos-overlay/+/1362397 I still cannot reproduce this error. The fuzzing target works in cros_fuzz --board-${BOARD} shell
,
Dec 5
is the problem related to this line from the stacktrace: "chown for "/tmp/.org.chromium.Chromium.ldRgmH/run/usb_bouncer" failed because: No such file or directory: Invalid argument" re #7: It's a pretty complicated beast (esp with minijail being involved): https://chrome-internal.googlesource.com/chrome/tools/clusterfuzz/+/master/src/python/bot/fuzzers/libFuzzer/launcher.py
,
Dec 5
I suspect /tmp isn't being created/mounted writable. I may submit a patch to fix the script it if I find the problem.
,
Dec 5
I don't think this is the case I think many fuzzers use /tmp (see: https://github.com/google/oss-fuzz/search?l=C&q=%2Ftmp) Code for that is here: https://chrome-internal.googlesource.com/chrome/tools/clusterfuzz/+/master/src/python/system/minijail.py#103 |
||||
►
Sign in to add a comment |
||||
Comment 1 by manojgupta@chromium.org
, Dec 2Owner: allenwebb@google.com
Status: Assigned (was: Untriaged)