- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add microsoft/win-dev-skills --skill windbg-user-ttd-reverse-debugging-triage -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add microsoft/win-dev-skills --skill windbg-user-ttd-reverse-debugging-triage -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add microsoft/win-dev-skills --skill windbg-user-ttd-reverse-debugging-triage -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add microsoft/win-dev-skills --skill windbg-user-ttd-reverse-debugging-triage -a grok -y복사한 메시지를 Grok Bot 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
Install this skill: https://github.com/microsoft/win-dev-skills/tree/HEAD/plugins/windbg/skills/windbg-user-ttd-reverse-debugging-triage게시자 제공
Load windbg-diagnostic-method first if it is not already loaded in this
conversation, and apply it throughout for evidence ranking, hypothesis testing,
confidence calibration, independent review, and report validation. This skill
adds the bug-family-specific commands and evidence requirements.
Time Travel Debugging records a user-mode process for replay, including an authorized application, service, or user-mode driver host process. A dump alone contains no execution timeline. Confirm a valid recording and matching module symbols before attempting timeline queries. It does not record kernel execution or automatically include another process's server-side activity.
Recording can change timing, require substantial storage, and capture sensitive memory. Obtain authorization before capture. Check the installed recorder's help for supported target, architecture, and options. WinDbg's Launch executable (advanced) / Record with Time Travel Debugging flow can record a named test application without guessing a recorder command.
Open the recorded .run file in WinDbg and load public Windows symbols and
matching PDBs for your own binaries.
!tt.index
dx @$cursession.TTD
Confirm the timeline range. Indexing and data-model availability depend on WinDbg/TTD versions; consult the installed help if the command is unavailable.
dx @$cursession.TTD.Calls("MyModule!MyFunction")
dx @$cursession.TTD.Memory(<start-address>, <end-address>, "w")
Query the known function or exact memory range, then inspect relevant results and their timeline positions. An empty result can mean unmatched symbols, uninstrumented execution, or an out-of-range query, not proof of absence.
Use the call query to find allocation/free or module lifetime transitions and the memory query to locate candidate writes. Account for allocator reuse: the same virtual address may represent different objects over the recording.
!tt <position>
k
r
g-
Seek to an actual position returned by the query. g- continues backward;
use the installed reverse-step controls to refine the search. Capture the
last-good and first-bad states, writer/caller stack, and ownership transition.
Do not equate the last write with the bug until you establish the object's identity, valid lifetime, intended invariant, and relevant cross-thread order.
For other user-mode families continue reasoning from the timeline rather than
dispatching to absent skills. For a kernel crash use windbg-kernel-bugcheck-triage;
TTD is not a kernel-history substitute.
Record the question, trace identity, timeline positions, relevant object lifetime, and source/stack evidence. Test alternatives and state recording boundaries. A reproducible timeline proves what occurred in that recording; it does not establish that instrumentation preserved all production timing.
Follow FEEDBACK.md and report a reviewed summary to
WinDbg-Feedback.
Include windbg-user-ttd-reverse-debugging-triage and the package version from
plugin.json; never automatically upload a recording or its memory/query
contents.
Use when an app, service, or user-mode driver host TTD recording is available and earlier calls, writes, or lifetimes matter. Not for kernel replay or history from a normal dump.
---name: windbg-user-ttd-reverse-debugging-triagedescription: Use when an app, service, or user-mode driver host TTD recording is available and earlier calls, writes, or…---# plugins/windbg/skills/windbg-user-ttd-reverse-debugging-triage/SKILL.mdFAQ
게시자에게서 plugins/windbg/skills/windbg-user-ttd-reverse-debugging-triage/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/microsoft/win-dev-skills에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.