* [WASM] Fix System.Core issues and disable broken tests.
* [wasm] Fix cookie computation heap overflow. Use a local to make it thread safe.
* [wasm] Disable System tests that don't work under WASM. Change the wasm profile to disable BSD sockets.
* [wasm] Address reviewer feedback.
* [wasm] Disable test that requires multiple threads.
* [wasm] Add package target to wasm.
* [wasm] Modify the runner to exit(1) if the test suite fails.
* [wasm] Add CI configuration for WebAssembly.
* [wasm] Fix issues found over review.
Reuse the existing icall infrastructure to give the same handle back.
This PR implements all OpenExisting methods (with the access rights parameter discarded) and the SafeHandle property.
In the runtime, we don't check the capacity parameter if we try to open a mmap file, and we fallthrough the handle refcount case.
This implements the icalls in file-mmap-windows.c used by MemoryMappedFile.
The implementation has been inspired by the CoreFX MemoryMappedFile
implementation.
This patch also fixes a few incompatibilities between .NET and Mono:
* The default MemoryMappedFileOptions has been changed from DelayAllocatePages
to None.
* mono_pagesize() on Windows now return SYSTEM_INFO.dwPageSize, the same as
.NET and CoreFX.
* Added mono_valloc_granule() which returns
SYSTEM_INFO.dwAllocationGranularity and changed mono-codeman.c to use it
when trying to allocate adjacent virtual memory.
* MemoryMappedFileTest has been updated to succeed on .NET.
* A test has been added to test correct DelayAllocatePages behavior (only
supported on Mono on Windows, the flag is ignored on other platforms).
* The posix MemoryMappedFile code has been changed to throw
UnauthorizedAccessException rather than IOException when trying to create a
view outside of the bounds of a MemoryMappedFile.
* Creating a named mapping larger than 4GB on 32-bit systems now throws
ArgumentOutOfRangeException.
NET_4_0 is always defined now, so the ifdefs are redundant.
I verified the libs are exactly the same after this change, so this is effectively a no-op.
Filled with Apple. From bug report:
The problem appears to be caused by a bug in mmap on the arm64 ios.
In this test, we request a page and mmap returns successfully, but when trying
to access the mapped memory, the program crashes after the 4097th byte, meaning
that it only maps us 4kb(???). It should be mentioned that on arm64 ios the
page size is 16kb.
This patch includes a few fixes:
* CreateNew will actually create a memory map file, the previous logic
in MemoryMapImpl.Open was wrong, and would fail if the file did not
exist. We now cope with this (bug #20052 was caused by this).
* Some exceptions were wrong, so this patch updates the
exceptions being thrown to be the right ones
* On Mobile, we inverted the logic to ensure that capacity must be
bigger or equal than the file size (which is what the API needs to do),
previously it performed the opposite test.
Added tests that match the behavior on .NET for this.