[Known Build Error] PrintException_TaskExceptionChain missing source-line annotations on Windows ARM64

Aperta
  • Qualcosa non va?
#6,190 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
49/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
cpp, csharp
Ambito
devtools, testing-qa

Direzione di ricerca

Start with the failing SOS.Tests.PrintExceptionTests.PrintException_TaskExceptionChain test and compare its expected source annotations with the Windows ARM64 build output. The issue links related bug #5909, but says the ARM64 failures have not been independently root-caused, so first determine whether the same cause applies. Done means the expected source-file and line annotations appear for the affected frames across the reported dump and debugger configurations.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Known Build Error

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1664616
Build error leg: Diagnostics Tests Helix win-arm64 Debug
Failing test: SOS.Tests.PrintExceptionTests.PrintException_TaskExceptionChain

Related bug: #5909 (!PrintException -lines drops source-line brackets for unwound exception stack frames in heap minidumps). The symptoms match; the ARM64 failures have not been independently root-caused.

Error Message

{
  "ErrorPattern": "expected: (output to contain \"RandomUserTask[.]cs @ 26\"|frame 'RandomTest[.]RandomUserTask[.]InnerException' to contain source annotation 'RandomUserTask[.]cs @ 38')",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Observed failures

On Windows ARM64, printexception -lines reports exception stack frames without the expected source-file/line annotation. Both CDB and dotnet-dump configurations fail.

.NET 9, Core / Dump / Workstation / Heap:

SOS assertion failed.
expected: output to contain "RandomUserTask.cs @ 26"

The RandomTest.RandomUserTask.<.ctor>b__2_0() frame is present, but its source annotation is missing.

.NET 10, Core / Dump / Workstation / Heap:

SOS assertion failed.
expected: frame 'RandomTest.RandomUserTask.InnerException' to contain source annotation 'RandomUserTask.cs @ 38'

The InnerException() frame is present without its source annotation; the following constructor-lambda frame still resolves to RandomUserTask.cs @ 22.

Independent reproductions

Build Branch / PR Observed failure
1664616 #6188, November 4, 2026 Both signatures: line 26 on .NET 9 and line 38 on .NET 10; CDB and dotnet-dump, Heap dumps.
1664227 main, November 4, 2026 Missing line 26 on .NET 9; CDB and dotnet-dump, Mini dumps.
1662417 #6010, November 3, 2026 Missing line 38 on .NET 9; CDB and dotnet-dump, Heap dumps.

Helix failure consoles:

These signatures predate #6188 and occur on unrelated changes. All eight GcInfo_ReportsEncoding cases passed in that PR's two failing work items.

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1664616
Error message validated: [expected: (output to contain "RandomUserTask[.]cs @ 26"|frame 'RandomTest[.]RandomUserTask[.]InnerException' to contain source annotation 'RandomUserTask[.]cs @ 38')]
Result validation: ❌ Known issue did not match with the provided build.
Validation performed at: 11/4/2026 10:21:31 PM UTC

Report
Build Repository Test Pull Request
1676372 dotnet/diagnostics SOS_win-arm64_Debug-Net9.WorkItemExecution dotnet/diagnostics#6209
1676182 dotnet/diagnostics SOS_win-arm64_Debug-Net9.WorkItemExecution dotnet/diagnostics#6217
1674501 dotnet/diagnostics SOS_win-arm64_Debug-Net9.WorkItemExecution dotnet/diagnostics#6210
1673441 dotnet/diagnostics SOS_win-arm64_Release-Net9.WorkItemExecution
1673440 dotnet/diagnostics SOS_win-arm64_Debug-Net9.WorkItemExecution dotnet/diagnostics#6208
1671643 dotnet/diagnostics SOS_win-arm64_Release-Net9.WorkItemExecution
1669587 dotnet/diagnostics SOS_win-arm64_Debug-Net9.WorkItemExecution
1668259 dotnet/diagnostics SOS_win-arm64_Debug-Net9.WorkItemExecution dotnet/diagnostics#6197
1666821 dotnet/diagnostics SOS_win-arm64_Debug-Net10.WorkItemExecution
1666677 dotnet/diagnostics SOS_win-arm64_Debug-Net9.WorkItemExecution dotnet/diagnostics#6194
1664784 dotnet/diagnostics SOS_win-arm64_Release-Net9.WorkItemExecution
1664616 dotnet/diagnostics SOS_win-arm64_Debug-Net9.WorkItemExecution dotnet/diagnostics#6188
Summary
24-Hour Hit Count 7-Day Hit Count 1-Month Count
2 10 12
Lingua principale
C++
Stelle
1.3k
Fork
407
Merge medio
21h 5m
PR unite (30g)
78

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

  • Nessun Dockerfile né file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di dotnet/diagnostics

Tutte le issue di dotnet/diagnostics

Issue simili

Altre issue su C++

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.