Problem
While running AI Dev Gallery with winapp run --aot --debug-output, the crash dump recorded an earlier, handled startup exception instead of the actual fatal exception.
Evidence from the same run:
|
Actual crash event |
Dump exception record |
| Thread |
14096 |
12008 |
| Exception |
0xC0000409 |
0xE06D7363 |
The dump's exception record matches a first-chance exception cached during startup. The actual crashing thread is present in the dump, but the reported stack contains only KERNELBASE!RaiseException. WinUI/XAML triage did run and captured additional stacks in the debug log.
Expected
Use the fatal event's thread and exception context as the primary crash context. Keep earlier first-chance information as clearly labeled supplemental diagnostics, rather than replacing the crash context.
Environment
CLI: 0.6.3-nmetulev-native-aot-publish-run.73, Windows x64, WinUI 3 NativeAOT app.
This was observed with NativeAOT, but appears to concern shared crash-dump handling. A minimal standalone repro is not yet available.
Problem
While running AI Dev Gallery with
winapp run --aot --debug-output, the crash dump recorded an earlier, handled startup exception instead of the actual fatal exception.Evidence from the same run:
0xC00004090xE06D7363The dump's exception record matches a first-chance exception cached during startup. The actual crashing thread is present in the dump, but the reported stack contains only
KERNELBASE!RaiseException. WinUI/XAML triage did run and captured additional stacks in the debug log.Expected
Use the fatal event's thread and exception context as the primary crash context. Keep earlier first-chance information as clearly labeled supplemental diagnostics, rather than replacing the crash context.
Environment
CLI:
0.6.3-nmetulev-native-aot-publish-run.73, Windows x64, WinUI 3 NativeAOT app.This was observed with NativeAOT, but appears to concern shared crash-dump handling. A minimal standalone repro is not yet available.