- name
SKILL.md
El archivo de la skill permanece en el repositorio del publicador.
Pega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add microsoft/win-dev-skills --skill windbg-user-mutex-held-across-co-await -a cursor -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add microsoft/win-dev-skills --skill windbg-user-mutex-held-across-co-await -a claude-code -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add microsoft/win-dev-skills --skill windbg-user-mutex-held-across-co-await -a codex -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add microsoft/win-dev-skills --skill windbg-user-mutex-held-across-co-await -a grok -yEnvía el mensaje copiado en un chat de Grok Bot. El Bot obtiene este SKILL.md de GitHub y lo añade a las skills que comparten todos tus Bots.
Install this skill: https://github.com/microsoft/win-dev-skills/tree/HEAD/plugins/windbg/skills/windbg-user-mutex-held-across-co-awaitDel publicador
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.
This pattern can occur in native application, service, or user-mode driver
code, including UMDF components that use C++ coroutines. Look for a lock
acquired before co_await and released after resumption or
coroutine destruction. Mutex ownership belongs to the acquiring thread, not
the coroutine frame. A resumption on another thread can violate that contract.
Even same-thread resumption can create reentrancy or progress problems when
the awaited operation needs a lock the coroutine still holds.
resume_background intentionally switches.
Do not assume every WinRT awaitable always resumes on a worker or always on
the originating thread.If the symptom is general blocking use windbg-user-wait-chain-analysis. For damaged
heap objects use windbg-user-heap-corruption-investigation. If a recording is available,
windbg-user-ttd-reverse-debugging-triage can help establish the ownership timeline.
Conceptual sequence, not a promise about any particular scheduler:
under lock:
take a snapshot and its generation
release lock
await work using that snapshot
under lock on the resumed thread:
revalidate generation, lifetime, and assumptions
apply result or explicitly handle a stale/cancelled operation
release lock
Use RAII for each synchronous scope. If invariants cannot tolerate unlocking,
redesign the operation or use a specifically designed asynchronous coordination
primitive with cancellation/lifetime rules. Switching to a recursive mutex or
shared_mutex does not make a thread-affine lock coroutine-safe.
Do not recommend a blanket mutex-type replacement. Shared locking is a separate design decision; changing the primitive does not repair suspension ownership. Keep the object and any captured interfaces alive across asynchronous work.
Follow FEEDBACK.md and report reviewed, sanitized feedback to
WinDbg-Feedback.
Include windbg-user-mutex-held-across-co-await and the package version from plugin.json;
no automatic source, dump, or transcript upload.
Use when app, service, or user-mode driver C++ coroutine code holds a thread-affine lock across suspension and later hangs or fails. Not for all coroutine crashes or choosing lock performance.
---name: windbg-user-mutex-held-across-co-awaitdescription: Use when app, service, or user-mode driver C++ coroutine code holds a thread-affine lock across suspension and…---# plugins/windbg/skills/windbg-user-mutex-held-across-co-await/SKILL.mdPreguntas frecuentes
Descarga plugins/windbg/skills/windbg-user-mutex-held-across-co-await/SKILL.md desde el publicador, o copia la ruta y abre el repositorio. PlugMCP lista la skill y no aloja el archivo.
El publicador lo mantiene en https://github.com/microsoft/win-dev-skills.
Claude, Cursor, Codex y Grok Build pueden leer un SKILL.md que añadas desde el repositorio del publicador. Grok Bot lo instala cuando envías en un chat el enlace a la carpeta de la skill en GitHub.