This happens frequently when launching GVE. We are setting ASAN_OPTIONS=/sdcard/asan.log. The logs contain an error message but no stack. We are using the build from https://firefox-ci-tc.services.mozilla.com/tasks/index/gecko.v2.mozilla-central.latest.mobile/android-x86_64-fuzzing-asan Any ideas or tips for debugging would be helpful. Contents of asan.log ``` at /sdcard/sanitizer_logs/report.log.8100 < ================================================================= ==8100==ERROR: AddressSanitizer: SEGV on unknown address 0x634db0180018 (pc 0x7a40cf152155 bp 0x000082f34aae sp 0x7ffe4c039580 T0) ==8100==The signal is caused by a READ memory access. at /sdcard/sanitizer_logs/report.log.8100 < ================================================================= ==8100==ERROR: AddressSanitizer: SEGV on unknown address 0x634db0180018 (pc 0x7a40cf152155 bp 0x000082f34aae sp 0x7ffe4c039580 T0) ==8100==The signal is caused by a READ memory access. ```
Bug 1658818 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
This happens frequently when launching GVE. We are setting `ASAN_OPTIONS=log_path=/sdcard/asan.log`. The logs contain an error message but no stack. We are using the build from https://firefox-ci-tc.services.mozilla.com/tasks/index/gecko.v2.mozilla-central.latest.mobile/android-x86_64-fuzzing-asan Any ideas or tips for debugging would be helpful. Contents of asan.log ``` at /sdcard/sanitizer_logs/report.log.8100 < ================================================================= ==8100==ERROR: AddressSanitizer: SEGV on unknown address 0x634db0180018 (pc 0x7a40cf152155 bp 0x000082f34aae sp 0x7ffe4c039580 T0) ==8100==The signal is caused by a READ memory access. at /sdcard/sanitizer_logs/report.log.8100 < ================================================================= ==8100==ERROR: AddressSanitizer: SEGV on unknown address 0x634db0180018 (pc 0x7a40cf152155 bp 0x000082f34aae sp 0x7ffe4c039580 T0) ==8100==The signal is caused by a READ memory access. ```