[Webkit-unassigned] [Bug 213200] New: REGRESSION(r262991): Broke stress/ensure-crash.js

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=213200

            Bug ID: 213200
           Summary: REGRESSION(r262991): Broke stress/ensure-crash.js
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: JavaScriptCore
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: mcatanzaro at gnome.org

Moving from bug #212479. stress/ensure-crash.js is broken since r262991 on Red Hat's internal cloop CI:

Running stress/ensure-crash.js.default
stress/ensure-crash.js.default: ERROR: Unexpected exit code: 134
FAIL: stress/ensure-crash.js.default
Running stress/ensure-crash.js.mini-mode
stress/ensure-crash.js.mini-mode: ERROR: Unexpected exit code: 134
FAIL: stress/ensure-crash.js.mini-mode

134 - 128 = 6 = SIGABRT on Linux, so the test is failing with SIGABRT. (SIGILL = 4 so if it were to exit with SIGILL its exit status would be 132.) Skimming the commit, I don't immediately see what could be causing a SIGABRT. I thought the most likely problem was that this change assumes HAVE(MACHINE_CONTEXT) is enabled, but looking in PlatformHave.h, that is not true on two of the four architectures we test (ppc64le and s390x). However, the test is failing in the same way on both x86_64 and aarch64, so that must not be the only problem here. I wonder if it might be related to ENABLE(SIGNAL_BASED_VM_TRAPS), which depends on DFG and is therefore disabled in cloop.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20200615/e082e47c/attachment-0001.htm>