Skip to content

Enable procdump first-chance exception monitoring for WinUI 3 test diagnostics#828

Open
Arlodotexe wants to merge 1 commit intomainfrom
feature/procdump-first-chance-exceptions
Open

Enable procdump first-chance exception monitoring for WinUI 3 test diagnostics#828
Arlodotexe wants to merge 1 commit intomainfrom
feature/procdump-first-chance-exceptions

Conversation

@Arlodotexe
Copy link
Member

@Arlodotexe Arlodotexe commented Feb 5, 2026

Summary

Adds procdump first-chance exception monitoring to CI test runs for UWP/WinAppSDK builds when \ENABLE_DIAGNOSTICS\ is true.

Changes

  • Monitors for first-chance exceptions using procdump -e 1 flag
  • Attaches to test process by name (CommunityToolkit.Tests.<multitarget>.exe)
  • Creates full memory dumps when first-chance exceptions occur

Motivation

Requested by @manodasanW for diagnosing intermittent WinUI 3 test failures. First-chance dumps will capture exceptions before they're caught/swallowed, providing better diagnostics than post-crash dumps.

Unblocks #817, Follow-up to #493, Contributes to fixing #347

This adds a procdump monitoring step before running component tests that:
- Monitors for first-chance exceptions using procdump -e 1 flag
- Attaches to the test process by name (CommunityToolkit.Tests.<multitarget>.exe)
- Creates full memory dumps when first-chance exceptions occur
- Only runs when ENABLE_DIAGNOSTICS is true and on uwp/wasdk builds

This helps capture crash information for exceptions that may be caught and
swallowed, providing better diagnostics for intermittent test failures.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant