Add positive cDAC loading policy tests with .NET 11 dumps

未关闭
#5,932 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
冷清
技术栈
cpp, linux

调研方向

从现有的 DbgShim.UnitTests negative/fallback cDAC 策略测试和诊断测试资产工作流开始。跟踪 IXCLRDataProcess 和 DBI ICorDebugProcess 的直接激活,然后为三种策略在 Windows 和 Linux 上添加 .NET 11 转储覆盖。完成的标准是 CI 证明 positive cDAC activation、provider selection 以及未改变的 legacy DAC behavior。

由索引模型根据 Issue 内容生成。

描述

Background

Dbgshim now has deterministic negative/fallback coverage for the cDAC loading policies by pointing DOTNET_CDAC_PATH at a nonexistent library. The tests verify LegacyDacOnly, PreferCDac, and CDacOnly for both direct IXCLRDataProcess activation and the DBI ICorDebugProcess path.

The current DbgShim.UnitTests dump assets are .NET 6, so they cannot positively validate activation through mscordaccore_universal. Positive coverage requires dumps generated from a compatible .NET 11 runtime and the matching cDAC/DBI artifacts.

Proposed work

  • Generate and publish Windows and Linux .NET 11 dump test assets using the existing diagnostics test-asset workflow.
  • Make the matching mscordaccore_universal and mscordbi available to DbgShim.UnitTests.
  • Add positive policy tests for both activation routes:
    • Direct data access requesting IXCLRDataProcess.
    • DBI activation requesting ICorDebugProcess.
  • Verify policy behavior:
    • CDacOnly succeeds without invoking the library provider.
    • PreferCDac succeeds through cDAC without invoking the fallback provider.
    • LegacyDacOnly uses the legacy DAC provider and succeeds.
  • Include Windows-hosted Linux cross-dump coverage so target platform detection and cDAC activation are exercised together.
  • Assert which path was used, not only that activation succeeded, using provider invocation counts and/or a test-visible activation signal.

Acceptance criteria

  • Positive cDAC activation is exercised in CI against a .NET 11 dump.
  • Direct data-access and DBI routes are both covered.
  • All three loading policies have independently identifiable test cases.
  • The tests prove cDAC success does not consult the fallback provider.
  • Legacy DAC behavior remains covered and unchanged.
主要语言
C++
星标
1.3k
派生
407
平均合并
21 小时 5 分钟
30 天内合并 PR
78

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

dotnet/diagnostics 的其他 Issue

查看 dotnet/diagnostics 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。