Closed Bug 1453609 Opened 7 years ago Closed 7 years ago

AddressSanitizer: odr-violation: global '<string literal>' at /builds/worker/workspace/build/src/js/src/jit/x86-shared/Constants-x86-shared.h:49:77

Categories

(Firefox :: Untriaged, defect)

61 Branch
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: rs, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36 Firefox for Android Actual results: ==17465==ERROR: AddressSanitizer: odr-violation (0x7f5b7cd0b000): [1] size=7 '<string literal>' /builds/worker/workspace/build/src/js/src/jit/x86-shared/Constants-x86-shared.h:49:77 [2] size=26 '<string literal>' /builds/worker/workspace/build/src/intl/icu/source/common/utypes.cpp:135:5 These globals were registered at these points: [1]: #0 0x43668e in __asan_register_globals /builds/worker/workspace/moz-toolchain/src/llvm/projects/compiler-rt/lib/asan/asan_globals.cc:358:3 #1 0x7f5b7b47017b in asan.module_ctor (/home/fuzzer/dev/firefox/libxul.so+0xe99b17b) [2]: #0 0x43668e in __asan_register_globals /builds/worker/workspace/moz-toolchain/src/llvm/projects/compiler-rt/lib/asan/asan_globals.cc:358:3 #1 0x7f5b6f1142cb in asan.module_ctor (/home/fuzzer/dev/firefox/libxul.so+0x263f2cb) ==17465==HINT: if you don't care about these errors you may set ASAN_OPTIONS=detect_odr_violation=0 SUMMARY: AddressSanitizer: odr-violation: global '<string literal>' at /builds/worker/workspace/build/src/js/src/jit/x86-shared/Constants-x86-shared.h:49:77 ==17465==ABORTING
Hi Francisco A., Can you please describe the steps that lead to this result? Is this an Android issue?
Flags: needinfo?(rs)
It was a Firefox (linux 64 build) issue. I've no testcase for this so far.
Flags: needinfo?(rs)
Thank you! I will close this issue as Resolved, Incomplete for now. Please feel free to reopen it when you have steps so we can reproduce the issue.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.