[cDAC] Improve logging

Open
#113,844 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
devtools

Research direction

Start by locating the cDAC failure paths and the SOS unit tests that capture their output; no file or entry point is named in the issue. Review how failures currently surface, then define completion as useful logging for most failure conditions with coverage in the relevant SOS test scenarios.

Written by the indexing model from the issue text.

Description

area-Diagnostics-cdac enhancement

Currently the cDAC does not log in most failure conditions.

While the output is not captured when running through SOS/WinDBG, the SOS unit tests do capture the output. In these scenarios improving logging will help debugging.

Dominant language
C#
Stars
18.3k
Forks
5.6k
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/runtime

All issues in dotnet/runtime

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.