ci-crash-dump

To retrieve crash dumps from failing Helix work items, apply this Skill to your dotnet CI runs to automatically identify crashed work items and download their crash artifacts. It fetches .dmp and .crashreport.json files along with console logs for inspection.

Debugging dotnet CI test crashes requires analyzing crash artifacts with dotnet-dump or cdb. This Skill provides step-by-step guidance for inspecting managed and native stacks, resolving symbols, and interpreting crash reports to pinpoint failure root causes.

Locating crashed Helix work items in PR builds is done by running the crash-dump analysis workflow against the failing CI run. This Skill identifies the specific crashed work items and retrieves their crash artifacts to guide your debugging process.

Yes, retrieving dotnet crash artifacts requires access to Helix APIs and crash artifact URLs. This Skill depends on these endpoints to identify crashed work items and download .dmp files, crash reports, and console logs for analysis.

Inspecting both managed and native stacks from a dotnet crash dump is supported using appropriate tooling like dotnet-dump or cdb. This Skill guides you through stack analysis to diagnose crashes across managed and native runtime layers.

When dotnet CI tests crash without clear errors, you need to analyze crash artifacts like .crashreport.json and .dmp files. This Skill helps identify the crashed Helix work items and retrieves these artifacts to reveal the underlying stack traces and failure reasons.