Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
GitHub or Developer Community with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
csharp> System.IO.MemoryMappedFiles.MemoryMappedFile.CreateFromFile ("/dev/mem");
This happens because MemoryMappedFile.Open () tries to obtain the size of the file, and /dev/mem has a size of 0.
Is there any way to work around this?
Looking at our implementation, we don't actually use the capacity anywhere other than for reporting exceptions when the MMF is created. I see now that this is a requirement of the API, but it seems like this effectively renders the API unusable on a lot of special Unix files.
Would it be reasonable to diverge from the API by allowing a capacity of zero?
I think its fine to change this on unix.
Restriction lifted in: https://github.com/mono/mono/commit/d8feb5e9adcc10e6733aedcc6aecee98b1a7c308