← WebKit — 2026-W37
e00002d2d87af12a8d1ab1fcc5c40802dd37c90f [JSC] Wasm debugger should resume breakpoints by dispatching the displaced opcode
not a security fix
confidence 0.1
signal score 12.9
Source/JavaScriptCore/llint
Classified as not security-relevant.
Triage note: Reworks the Wasm IPInt debugger trap protocol (DebuggerTrapStatus bool -> resume OpType) and the ENABLE(WEBASSEMBLY_DEBUGGER) BreakpointManager to pc-keyed patches with hasSite/step refcounting. Developer debugger infrastructure not reachable from web content.
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: Reworks the Wasm IPInt debugger trap protocol (DebuggerTrapStatus bool -> resume OpType) and the ENABLE(WEBASSEMBLY_DEBUGGER) BreakpointManager to pc-keyed patches with hasSite/step refcounting. Developer debugger infrastructure not reachable from web content.
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), null_guard (+1.95), large_churn (-2.0)
Before / after
Loading diff…
On This Page