Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: f2bd414de34774442eb86b4b84ed8e3263386822
https://github.com/WebKit/WebKit/commit/f2bd414de34774442eb86b4b84ed8e3263386822
Author: Yijia Huang <[email protected]>
Date: 2026-09-14 (Mon, 14 Sep 2026)
Changed paths:
M JSTests/wasm/debugger/tests/tests.py
M Source/JavaScriptCore/wasm/debugger/WasmExecutionHandler.cpp
Log Message:
-----------
[JSC] Don't self-deadlock the WASM debug server on an unknown thread id
https://bugs.webkit.org/show_bug.cgi?id=324171
rdar://187396893
Reviewed by Yusuke Suzuki and Keith Miller.
handleThreadStopInfo() holds ExecutionHandler::m_lock while calling
sendStopReplyForThread(), whose miss path replied via sendErrorReply(). That
routes back into ExecutionHandler::sendReply(), which takes m_lock again, and
WTF::Lock is not recursive, so the server parked on its own lock and answered
nothing further. Both early returns now use sendReplyImpl(locker, ...), as the
success path in the same function already did.
Tests:
JSTests/wasm/debugger/tests/tests.py: ThreadStopInfoUnknownThreadTestCase
Canonical link: https://commits.webkit.org/321108@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
