← WebKit — 2026-W38
d8d35775495697d094af498ab4e726cdff9aa029 [JSC] Decide on the pre-patch opcode, not the patched byte, in the WASM debugger
not a security fix
confidence 0.12
signal score 12.95
Source/JavaScriptCore/wasm
Classified as not security-relevant.
Triage note: Replaces m_addressToPC with m_addressToBreakpoint, adds originalOpcodeAt() so setStepIntoBreakpointForThrow reads the un-patched TryTable opcode rather than a patched 0x00 byte, and types originalBytecode as OpType; wasm debug-server correctness, not web-reachable.
This commit was flagged by the signal scorer and reviewed by AI (not a human). It is listed only so the triage is auditable; there is no root-cause analysis because this is not a vulnerability fix.
Triage note: Replaces m_addressToPC with m_addressToBreakpoint, adds originalOpcodeAt() so setStepIntoBreakpointForThrow reads the un-patched TryTable opcode rather than a patched 0x00 byte, and types originalBytecode as OpType; wasm debug-server correctness, not web-reachable.
This commit was flagged by the signal scorer and reviewed by AI (not a human). It is listed only so the triage is auditable; there is no root-cause analysis because this is not a vulnerability fix.
Structural signals: smartptr_member_added (+6.47), security_assert (+6.47)
Before / after
Loading diff…
On This Page