Open EgorBo opened 4 months ago
/cc @steveisok
This happens because it eventually calls Buffer:Memmove, which doesn't throw for null/null because of these lines:
if (((nuint)(nint)Unsafe.ByteOffset(ref src, ref dest) < len) || ((nuint)(nint)Unsafe.ByteOffset(ref dest, ref src) < len))
{
goto BuffersOverlap;
}
BuffersOverlap:
// If the buffers overlap perfectly, there's no point to copying the data.
if (Unsafe.AreSame(ref dest, ref src))
{
return;
}
Actually, given it's windows x64 mono, we probably won't fix this.
This is a disabled test issue, and it's marked for all platforms. So we should update issues.targets before closing; also we should validate what happens on non-Windows platforms
The test I am adding in https://github.com/dotnet/runtime/pull/98623 fails on mono (at least on
mono windows x64 Release @ Windows.10.Amd64.Open
- logs. probably will fail on other pipelines as well).