docs(#501/#512): case study — attaching the debugger to itself - #516
Merged
Conversation
Documents the #501 dogfooding session: the fork-release fix, the residual 0/6 self-attach failure it exposed, the strace heisenbug, root-causing the lost init ACK by live-patching the subject through its own evaluate_expression, and the #512 latch fix that took the stress harness to 6/6. Links the side findings (#513, the #502 negative result, the unexplained one-time SIGKILL) and the takeaways. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NgA5kHzkhFZLqbWNZRTsVG
debugmcpdev
enabled auto-merge (squash)
August 27, 2026 14:19
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
debugmcpdev
added a commit
that referenced
this pull request
Aug 27, 2026
The full RCA narrative behind PR #522: how a js attach pause_execution could return success forever without pausing anything, why the routing hole a code-reading pass produced was real but not the field mechanism (js-debug's smart-stepper converting user pauses into an endless step chase through internal frames was), the adapterConfig {trace: true} technique that made the adapter narrate its own CDP decisions, and the third bug the fix's e2e caught that interactive repro timing could not reach (pre-adoption dispatch swallowed without a response). Side findings link to the issues they became: #518 (trace parent/child discriminator), #519 (routing logs invisible in the per-session proxy log), #520 (ensureInitialStop's 12s threads poll on js attach). Continues the docs/case-studies series (#510, #516); README links it. Claude-Session: https://claude.ai/code/session_01XtvNu3aNB1nw1URRL5UTgR Co-authored-by: CI Bot <ci@example.com> Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
docs/case-studies/self-attach-fork-release-and-the-500ms-ack-window.md(linked from the README next to the existing rdbg case study): the #501 fork-release fix (#514), the residual self-attach failure it exposed, the strace heisenbug, root-causing the lost init ACK (#512, #515) by live-patching the subject through its ownevaluate_expression, and the side findings (#513, the #502 negative result, one unexplained SIGKILL).🤖 Generated with Claude Code
https://claude.ai/code/session_01NgA5kHzkhFZLqbWNZRTsVG