Bug 1883865 Comment 7 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
(In reply to Christian Holler (:decoder) from comment #3)
]> Runtime options: --no-threads --wasm-compiler=baseline
> 
> Backtrace:
> 
>     ==639==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000008 (pc 0x55c327c835c8 bp 0x7fff7ca71900 sp 0x7fff7ca71870 T0)
>     ==639==The signal is caused by a READ memory access.
>         #0 0x55c327c835c8 in InlineForwardListIterator /js/src/jit/InlineList.h:151:29
...
>         #7 0x55c32840f536 in js::jit::GenerateLIR(js::jit::MIRGenerator*) /js/src/jit/Ion.cpp:1551:23
>         #8 0x55c328cbeb0d in js::wasm::IonCompileFunctions(js::wasm::ModuleEnvironment const&, js::wasm::CompilerEnvironment const&, 


I noticed that test is running with --wasm-compiler=baseline which shall disable Ion, but stack trace clearly shows Ion is running. Is it a mistake?
Revision 1 by
on 
(In reply to Christian Holler (:decoder) from comment #3)
> Runtime options: --no-threads --wasm-compiler=baseline
> 
> Backtrace:
> 
>     ==639==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000008 (pc 0x55c327c835c8 bp 0x7fff7ca71900 sp 0x7fff7ca71870 T0)
>     ==639==The signal is caused by a READ memory access.
>         #0 0x55c327c835c8 in InlineForwardListIterator /js/src/jit/InlineList.h:151:29
...
>         #7 0x55c32840f536 in js::jit::GenerateLIR(js::jit::MIRGenerator*) /js/src/jit/Ion.cpp:1551:23
>         #8 0x55c328cbeb0d in js::wasm::IonCompileFunctions(js::wasm::ModuleEnvironment const&, js::wasm::CompilerEnvironment const&, 


I noticed that test is running with --wasm-compiler=baseline which shall disable Ion, but stack trace clearly shows Ion is running. Is it a mistake?

Back to Bug 1883865 Comment 7