Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: 7e7a59f05cf089d89b7c13f449839b674c783af3
https://github.com/WebKit/WebKit/commit/7e7a59f05cf089d89b7c13f449839b674c783af3
Author: Yijia Huang <[email protected]>
Date: 2026-04-17 (Fri, 17 Apr 2026)
Changed paths:
M JSTests/wasm/debugger/resources/swift-wasm/build.sh
A JSTests/wasm/debugger/resources/swift-wasm/fatal-error-test/Package.swift
A
JSTests/wasm/debugger/resources/swift-wasm/fatal-error-test/Sources/fatal-error-test/main.swift
A
JSTests/wasm/debugger/resources/swift-wasm/fatal-error-test/fatal-error-test.wasm
A JSTests/wasm/debugger/resources/swift-wasm/fatal-error-test/main.js
M JSTests/wasm/debugger/tests/tests.py
Log Message:
-----------
[JSC][WASM][Debugger] Add Swift fatalError trap test
https://bugs.webkit.org/show_bug.cgi?id=312592
rdar://175024728
Reviewed by Keith Miller.
Add a new Swift WASM test (fatal-error-test) that verifies the debugger
correctly intercepts a Swift fatalError() trap. Swift's _assertionFailure
triggers an out-of-bounds memory access in the minimal WASI stub environment,
which the debugger intercepts as an "Out of bounds memory access" stop. The
test confirms reliable fault interception across 10 iterations and that the
backtrace includes the fatalError call site at main.swift:4.
fd_write is implemented properly (writing nwritten back to memory) to prevent
Swift's runtime from spinning in a retry loop when attempting to print the
error message.
Also bumps the Swift WASM SDK version in build.sh from 6.2.3 to 6.3.1.
Canonical link: https://commits.webkit.org/311466@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
