1429140 - timeout function doesn't work when ion is disabled

Status: RESOLVED FIXED

(Core :: JavaScript Engine, defect)

Description

[Robin Templeton [:terpri]]

The JS shell's "timeout" function doesn't work when Ion is disabled (using the "--disable-ion" configure option). For example, "js -e 'timeout(1);sleep(2)'" segfaults in the ContextToPC function from js/src/wasm/WasmSignalHandlers.cpp. This causes test failures that don't happen when the JIT is enabled.

Comment 1

[Robin Templeton [:terpri]]

This problem seems to have been present since the non-Ion build was fixed in #1388005.

Comment 2

[Lars T Hansen [:lth]]

Disabling signal handling for JS_CODEGEN_NONE makes the test case run (I have a simple patch).  Also, when running jit-tests on a JS_CODEGEN_NONE build that patch changes crash failures into simple test failures, which is at least something.  But there are still quite a few test failures on jit-tests, failures I do not see when running with --no-ion --no-baseline, for example.  So the proper fix is likely to try to make signal handling work properly for the JS_CODEGEN_NONE build.  This seems doable, there are a couple of likely places where we can bypass attempts to identify JIT code (which is what currently fails).

Comment 3

[Lars T Hansen [:lth]]

Attachment: bug1429140-non-ion-signal-handling.patch

See commit message for technical details.  With this patch, a --disable-ion build passes all jit-tests.

Comment 4

[Luke Wagner [:luke]]

Comment on attachment 8941877 [details] [diff] [review]
bug1429140-non-ion-signal-handling.patch

Review of attachment 8941877 [details] [diff] [review]:
-----------------------------------------------------------------

Thanks!

Comment 5

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/mozilla-inbound/rev/16740cf93a77
Make signal handling work for --disable-ion builds. r=luke

Comment 6

[Narcis Beleuzu [:NarcisB]]

https://hg.mozilla.org/mozilla-central/rev/16740cf93a77