Debugger report null for uninited static struct field in classes without an .cctor

[yyjdelete]

Description

Debugger will report null instead of default(...) for uninited static field(struct) in classes without an static ctor. It's an value type and should never be null.
Get null when watch the field in debugger, and ArgumentNullException when try to access any member of the field in debugger.

It only affect the debugger, running the program can get the right result. And after access the field in program or add an static ctor, the debugger can also get the right value.

Configuration

Which version of .NET is the code running on: netcoreapp2.1/3.1/net5.0(x64)
What OS and version, and what distro if applicable: win10 x64(2004)
What is the architecture (x64, x86, ARM, ARM64): x64
Debugger: VS/VSCode

Regression?

This seems happen on all version of netcore(not tested with 1.x), but not happen on any version of netframework(tested with net48), not sure if it's an issue of runtime or debugger of VS.

Other information

See null for Program.dateTime in debugger before Console.WriteLine and 0001-01-01 after Console.WriteLine

using System;
using System.Diagnostics;

namespace ConsoleApp7
{
    class Program
    {
        public static DateTime dateTime;

        static void Main(string[] args)
        {
            Debugger.Break();
            Console.WriteLine(Program.dateTime);
        }
    }
}

[ghost]

Tagging subscribers to this area: @tommcdon
See info in area-owners.md if you want to be subscribed.

[dotnet-policy-service]

Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

This process is part of our issue cleanup automation.

[dotnet-policy-service]

This issue will now be closed since it had been marked no-recent-activity but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.