[ci-scan] Hang: dotnet-dump opening macOS x64 Mach-O dumps

オープン
  • 何か問題がありますか？
#137,115 コメント 3 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
35/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
停滞
技術スタック
csharp, macos
領域
devtools, operating-systems

調査の方向性

The issue identifies the Mach-O parser regression in ClrMD, introduced by microsoft/clrmd#1523 and brought into diagnostics through dotnet/diagnostics#6191. Start by reading those changes and the SOS replay; the failure occurs while opening a macOS x64 dump, when LC_THREAD alignment padding is treated as another thread-state header. Done means dotnet-dump opens the dump and the affected SOS tests emit their startup marker.

索引モデルが issue の本文から書いたものです。

説明

area-Diagnostics-cdac blocking-clean-ci disabled-test Known Build Error

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1668244
Build error leg or test failing: runtime-diagnostics osx-x64 release SOS and SOS_EnumMemory - SOS.Tests
Pull request: https://github.com/dotnet/runtime/pull/137102

KBE authoring guidance (ci-failure-scan)
  • Error Details is for readers. Paste the full exception, stack trace, or build error excerpt so the failure is understandable without opening the raw log.
  • Build Analysis parses only the single JSON block under Error Message.
  • ErrorMessage is a case-sensitive ordinal String.Contains substring copied verbatim from the failing log.
  • Set BuildRetry to true only for a clear infrastructure retry case. ExcludeConsoleLog disables Helix console-log scanning.

Error Details

System.InvalidOperationException : Dump session command failed:
Host=DotnetDump
Flavor=Core
CoreVersion=Net11
Dac=Legacy or CDac
HostRuntime=Managed
---- System.TimeoutException : dotnet-dump did not return output for '<startup>' within 00:02:00.

Captured dotnet-dump startup output:
Loading core dump: ...
Truncated Mach-O thread state header.

The failure occurs before DAC selection and affects both the Legacy DAC and cDAC configurations. The SOS replay shows that dotnet-dump fails while opening the Mach-O dump, then does not emit the test harness startup marker.

The regression was introduced by microsoft/clrmd#1523 and flowed into diagnostics through dotnet/diagnostics#6191. The updated parser treats the required four-byte alignment padding at the end of the x64 LC_THREAD command as another thread-state header. Runtime's dump writer intentionally includes this padding because 64-bit Mach-O load commands must be eight-byte aligned.

The same failure reproduces on unrelated runtime PRs, including #137103. A runtime-diagnostics build using diagnostics commit 93559c0 passed; builds using diagnostics after the ClrMD dependency update fail the macOS x64 SOS legs.

Error Message

{
  "ErrorMessage": "System.TimeoutException : dotnet-dump did not return output for '<startup>' within 00:02:00.",
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}
Agentic workflow metadata (ci-failure-scan)

Workflow artifact: ci-failure-scan
Artifact kind: kbe-verification
Verified match count: 274 hits in failure.log

[!NOTE]
This issue was generated with the assistance of GitHub Copilot.

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1668244
Error message validated: [System.TimeoutException : dotnet-dump did not return output for '<startup>' within 00:02:00.]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 11/6/2026 10:45:00 PM UTC

Report
Build Repository Test Pull Request
1669708 dotnet/runtime SOS_osx-x64_Release-Net11.WorkItemExecution dotnet/runtime#136983
1669572 dotnet/runtime SOS_osx-x64_Release-Net11.WorkItemExecution dotnet/runtime#136973
1669329 dotnet/runtime SOS_osx-x64_Release-Net11.WorkItemExecution dotnet/runtime#136973
1669356 dotnet/runtime SOS_osx-x64_Release-Net11.WorkItemExecution dotnet/runtime#136770
1668891 dotnet/runtime SOS_osx-x64_Release-Net11.WorkItemExecution dotnet/runtime#136983
1668842 dotnet/runtime SOS_osx-x64_Release-Net11.WorkItemExecution
1668771 dotnet/runtime SOS_osx-x64_Release-Net11.WorkItemExecution dotnet/runtime#137119
1668753 dotnet/runtime SOS_osx-x64_Release-Net11.WorkItemExecution dotnet/runtime#137103
1668641 dotnet/runtime SOS_osx-x64_Release-Net11.WorkItemExecution dotnet/runtime#137113
1668662 dotnet/runtime SOS_osx-x64_Release-Net11.WorkItemExecution dotnet/runtime#137112
1668670 dotnet/runtime SOS_osx-x64_Release-Net11.WorkItemExecution dotnet/runtime#137114
1668609 dotnet/runtime SOS_osx-x64_Release-Net11.WorkItemExecution dotnet/runtime#137102
1668541 dotnet/runtime SOS_osx-x64_Release-Net11.WorkItemExecution dotnet/runtime#136611
1668469 dotnet/runtime SOS_osx-x64_Release-Net11.WorkItemExecution dotnet/runtime#136973
1668491 dotnet/runtime SOS_osx-x64_Release-Net11.WorkItemExecution dotnet/runtime#136983
1668480 dotnet/runtime SOS_osx-x64_Release-Net11.WorkItemExecution dotnet/runtime#136770
1668393 dotnet/runtime SOS_osx-x64_Release-Net11.WorkItemExecution dotnet/runtime#137108
1668244 dotnet/runtime SOS_osx-x64_Release-Net11.WorkItemExecution dotnet/runtime#137102
Summary
24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 18 18
主要言語
C#
スター
18.4k
フォーク
5.8k
平均マージ
2日 19時間
マージ済み PR（30日）
590

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

dotnet/runtime のほかの issue

dotnet/runtime の issue をすべて見る

似ている issue

C# の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。