Mikhail Kurinnoi

Hmm... strange, because `HasValue` code is https://github.com/dotnet/runtime/blob/135fec006e727a31763271984cd712f1659ccbd3/src/libraries/System.Private.CoreLib/src/System/Nullable.cs#L33-L37 ``` public readonly bool HasValue { [NonVersionable] get => hasValue; } ``` and `hasValue=false, HasValue = true` could happens only in case https://github.com/dotnet/runtime/blob/135fec006e727a31763271984cd712f1659ccbd3/src/libraries/System.Private.CoreLib/src/System/Nullable.cs#L27-L31...

Hmm... looks like works different for ```public double? DoubleValue;``` and ```public double? DoubleValue{get;set;}```. Will add this in investigation list.

Did you try `-gdb-set just-my-code 0` before attach to process? Please note, in case of launch, debugger disable code optimization for each assembly during loading (this is especially need for...

> Will this be fixed? Inside debugger? No. This is not debugger related issue, but related to .NET runtime work itself. In case assembly load with "optimized" flag and have...

Debugger use runtime debug API, that provide callbacks and call this callbacks at "stop" events like step complete, exception, breakpoints,... if assert related logic don't call callbacks and just print...

As you probably noticed, debugger don't provide stop events in code without PDB and this have a reason. Related to this issue fix should care about "special" status of process...

> Host: > Architecture: arm64 Please note, at this moment we don't support Mac M1 (arm64). You can't use amd64 binary, that we provide, with arm64 .Net SDK. See related...

`DebuggerDisplayAttribute` not supported for now and probably will not be implemented in near future, since require special parser for expressions and expression evaluation we don't have implemented yet.